Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b9ff77b87575a655fe5a69592626d32627be1031f5a49a7fa504eab4d7413c7f

Tx prefix hash: 4337ec13e03049493eb74bbca3be8a1ea0d1904c55cbca6bafa4d7d294b3738e
Tx public key: e5bfef797c48dd03db1f7a15f06a07565cc1b6ba53c97c993972305c5e553cd8
Timestamp: 1728108417 Timestamp [UCT]: 2024-10-05 06:06:57 Age [y:d:h:m:s]: 00:232:05:09:40
Block: 1124775 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 165802 RingCT/type: yes/0
Extra: 01e5bfef797c48dd03db1f7a15f06a07565cc1b6ba53c97c993972305c5e553cd802110000000291e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ef40d59da36edec7b148739b9d9d507dce55112c0b012a84c59b5aaa9c8958f 0.600000000000 1607444 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": 1124785, "vin": [ { "gen": { "height": 1124775 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ef40d59da36edec7b148739b9d9d507dce55112c0b012a84c59b5aaa9c8958f" } } ], "extra": [ 1, 229, 191, 239, 121, 124, 72, 221, 3, 219, 31, 122, 21, 240, 106, 7, 86, 92, 193, 182, 186, 83, 201, 124, 153, 57, 114, 48, 92, 94, 85, 60, 216, 2, 17, 0, 0, 0, 2, 145, 225, 60, 4, 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