Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3a6b5d1fc5096b2d0004456f16cd84ae8c4c3a1479692e512a24152424e4d70c

Tx prefix hash: ee7fcd32e0c0766be290217f3d3fc06eedd68507641a8f59381ce7d998de9089
Tx public key: 345df4d7e33fe8361ef37ccfc1b7d58a4a7e7d7974a55b1b3e9a3192c54caada
Timestamp: 1736782813 Timestamp [UCT]: 2025-01-13 15:40:13 Age [y:d:h:m:s]: 00:064:19:06:34
Block: 1196547 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46108 RingCT/type: yes/0
Extra: 01345df4d7e33fe8361ef37ccfc1b7d58a4a7e7d7974a55b1b3e9a3192c54caada0211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c0ae8ca36c52c8dd0a626dc19500bdf6154317188590799bc174cad23b6fe1f5 0.600000000000 1683146 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": 1196557, "vin": [ { "gen": { "height": 1196547 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c0ae8ca36c52c8dd0a626dc19500bdf6154317188590799bc174cad23b6fe1f5" } } ], "extra": [ 1, 52, 93, 244, 215, 227, 63, 232, 54, 30, 243, 124, 207, 193, 183, 213, 138, 74, 126, 125, 121, 116, 165, 91, 27, 62, 154, 49, 146, 197, 76, 170, 218, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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