Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db016b8b51f29bd7e53b34154ca344e72faa79ff4d672f4924d27e872022deaf

Tx prefix hash: 285779f9881512f732322c0fa1f427207f87dc555763c4549d4b8baaa6ecdb33
Tx public key: 858ca68fd415925864759cc2f36f2fd15607f4e56e83922c57e7d1acbee40042
Timestamp: 1701965205 Timestamp [UCT]: 2023-12-07 16:06:45 Age [y:d:h:m:s]: 01:128:16:59:02
Block: 908040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 353138 RingCT/type: yes/0
Extra: 01858ca68fd415925864759cc2f36f2fd15607f4e56e83922c57e7d1acbee40042021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.601570466000 dcy

stealth address amount amount idx
00: ebd5934b23d3ca7b7bebc57cf043c3a11b23d9be1d5c2f5f904c22d1de75b858 0.601570466000 1365051 of 0

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": 908050, "vin": [ { "gen": { "height": 908040 } } ], "vout": [ { "amount": 601570466, "target": { "key": "ebd5934b23d3ca7b7bebc57cf043c3a11b23d9be1d5c2f5f904c22d1de75b858" } } ], "extra": [ 1, 133, 140, 166, 143, 212, 21, 146, 88, 100, 117, 156, 194, 243, 111, 47, 209, 86, 7, 244, 229, 110, 131, 146, 44, 87, 231, 209, 172, 190, 228, 0, 66, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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