Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ed3872d5624975e2e94762222cb9882cfa1bfaddb3e72c3cafaa21684e93d38

Tx prefix hash: a600fcc051396eb71f75ef2b9eb66cf7f749e7a833850886b4846934c92cb1cc
Tx public key: 0e25e5df9b840926b9cb01a1fc7596cd11a344457dbe1a312ab8997e3aa37491
Timestamp: 1737100716 Timestamp [UCT]: 2025-01-17 07:58:36 Age [y:d:h:m:s]: 00:337:18:37:12
Block: 1199178 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 238965 RingCT/type: yes/0
Extra: 010e25e5df9b840926b9cb01a1fc7596cd11a344457dbe1a312ab8997e3aa37491021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 409b34564d346ce4153bd004eb7a6f0e29c6bc7677d9470624aa28c136ee50f5 0.600000000000 1685807 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": 1199188, "vin": [ { "gen": { "height": 1199178 } } ], "vout": [ { "amount": 600000000, "target": { "key": "409b34564d346ce4153bd004eb7a6f0e29c6bc7677d9470624aa28c136ee50f5" } } ], "extra": [ 1, 14, 37, 229, 223, 155, 132, 9, 38, 185, 203, 1, 161, 252, 117, 150, 205, 17, 163, 68, 69, 125, 190, 26, 49, 42, 184, 153, 126, 58, 163, 116, 145, 2, 17, 0, 0, 0, 5, 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