Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a2d659c9ae477e18593f7c2b2cb2ae0bf34fcf2e7b011b79b9283c95a7921c9a

Tx prefix hash: 4b96222168f21899cc4d22e5a8decad05704e629ff0ac398d5a5fffe04039373
Tx public key: dc1087f99e214d4ca65e948956545dbc7f4c45e11830aa5aedaec2b1245929c3
Timestamp: 1723383254 Timestamp [UCT]: 2024-08-11 13:34:14 Age [y:d:h:m:s]: 00:234:19:04:05
Block: 1085612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167676 RingCT/type: yes/0
Extra: 01dc1087f99e214d4ca65e948956545dbc7f4c45e11830aa5aedaec2b1245929c302110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a9b1cdaf66d2eee5e5d1203e5ab8bbaabc8b2f89bc6c38959738025db4d7096 0.600000000000 1560199 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": 1085622, "vin": [ { "gen": { "height": 1085612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a9b1cdaf66d2eee5e5d1203e5ab8bbaabc8b2f89bc6c38959738025db4d7096" } } ], "extra": [ 1, 220, 16, 135, 249, 158, 33, 77, 76, 166, 94, 148, 137, 86, 84, 93, 188, 127, 76, 69, 225, 24, 48, 170, 90, 237, 174, 194, 177, 36, 89, 41, 195, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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