Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: da56034c13c3be40037317a2b05d87b95b2afa7007dbd90627a0d7d1a6a2252f

Tx prefix hash: a6474a4ea3843725296fc0fe01afcf52309788c935845745d8a256d27095ff58
Tx public key: 1dc4e0ff512f3bc8dde17057aa9f0d39bfe69af4acb8bb7e2499815b73edaa94
Timestamp: 1713308787 Timestamp [UCT]: 2024-04-16 23:06:27 Age [y:d:h:m:s]: 01:007:15:09:56
Block: 1002066 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266422 RingCT/type: yes/0
Extra: 011dc4e0ff512f3bc8dde17057aa9f0d39bfe69af4acb8bb7e2499815b73edaa9402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b752291bc9384df6047b74e4427d50bbae5467b7b5b9f63ea5e0c8f73fbcd92 0.600000000000 1462580 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": 1002076, "vin": [ { "gen": { "height": 1002066 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b752291bc9384df6047b74e4427d50bbae5467b7b5b9f63ea5e0c8f73fbcd92" } } ], "extra": [ 1, 29, 196, 224, 255, 81, 47, 59, 200, 221, 225, 112, 87, 170, 159, 13, 57, 191, 230, 154, 244, 172, 184, 187, 126, 36, 153, 129, 91, 115, 237, 170, 148, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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