Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 0e58a5b34d8bc52ea15f512a626e799b5e7f01ae41d4b42373c35a2b744a91f1

Tx prefix hash: 53c72875bbb4577ca2d93acce17011cbdaa81eb671208042135dec5ce22433bc
Tx public key: abd79a77d0be6bf71437a7057f30378b5a96cfdf7016f6c79562e346edfbf53f
Timestamp: 1736244696 Timestamp [UCT]: 2025-01-07 10:11:36 Age [y:d:h:m:s]: 00:097:23:04:25
Block: 1192096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69801 RingCT/type: yes/0
Extra: 01abd79a77d0be6bf71437a7057f30378b5a96cfdf7016f6c79562e346edfbf53f021100000009007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2c3ca7fd0b30c87f798c778ccc9e1d5540670f9ed56abbf1e0adb6e02f60c80b 0.600000000000 1678641 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1192106, "vin": [ { "gen": { "height": 1192096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2c3ca7fd0b30c87f798c778ccc9e1d5540670f9ed56abbf1e0adb6e02f60c80b" } } ], "extra": [ 1, 171, 215, 154, 119, 208, 190, 107, 247, 20, 55, 167, 5, 127, 48, 55, 139, 90, 150, 207, 223, 112, 22, 246, 199, 149, 98, 227, 70, 237, 251, 245, 63, 2, 17, 0, 0, 0, 9, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8