Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c62dc658e744d297011bb2d4a42926eb1eb5bf55486036493502720b61655732

Tx prefix hash: 2b9fdfb0055930f444fe6c838c4256523ed4a865f50c9c86052b4c73a9b440a8
Tx public key: 5e88fb9395910b8abca1e99764792c9d2df478d9f493de471df48a8ee13b0fcf
Timestamp: 1633222327 Timestamp [UCT]: 2021-10-03 00:52:07 Age [y:d:h:m:s]: 03:159:20:33:00
Block: 345492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 891031 RingCT/type: yes/0
Extra: 015e88fb9395910b8abca1e99764792c9d2df478d9f493de471df48a8ee13b0fcf02110000005e8d0de867000000000000000000

1 output(s) for total of 43.978662068000 dcy

stealth address amount amount idx
00: 6f752f8f8f50a7f649859e26765fb227b7e916f0ea86f45825cd0519d77fb5c6 43.978662068000 708708 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": 345502, "vin": [ { "gen": { "height": 345492 } } ], "vout": [ { "amount": 43978662068, "target": { "key": "6f752f8f8f50a7f649859e26765fb227b7e916f0ea86f45825cd0519d77fb5c6" } } ], "extra": [ 1, 94, 136, 251, 147, 149, 145, 11, 138, 188, 161, 233, 151, 100, 121, 44, 157, 45, 244, 120, 217, 244, 147, 222, 71, 29, 244, 138, 142, 225, 59, 15, 207, 2, 17, 0, 0, 0, 94, 141, 13, 232, 103, 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