Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 13dfd192f3d2be9f7e1ed372734c2a8bea9dc9751b3f7ecbf7ddc20f28b43ac2

Tx prefix hash: 6e81354e0084dc17dbbf60539ebc89eef96746ab3e6fe234529a9b52131750d6
Tx public key: ee44253e2ab91886b23baa761ff9171bad68585dce00313f40bcaaad80f703cb
Timestamp: 1699059778 Timestamp [UCT]: 2023-11-04 01:02:58 Age [y:d:h:m:s]: 01:165:17:03:49
Block: 884155 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 379424 RingCT/type: yes/0
Extra: 01ee44253e2ab91886b23baa761ff9171bad68585dce00313f40bcaaad80f703cb02110000000733af99f4000000000000000000

1 output(s) for total of 0.721817590000 dcy

stealth address amount amount idx
00: bcbc63dbb673a6e63d150b16db0420b9934f9b81c36df7dca2c40c58757f4e6b 0.721817590000 1339888 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": 884165, "vin": [ { "gen": { "height": 884155 } } ], "vout": [ { "amount": 721817590, "target": { "key": "bcbc63dbb673a6e63d150b16db0420b9934f9b81c36df7dca2c40c58757f4e6b" } } ], "extra": [ 1, 238, 68, 37, 62, 42, 185, 24, 134, 178, 59, 170, 118, 31, 249, 23, 27, 173, 104, 88, 93, 206, 0, 49, 63, 64, 188, 170, 173, 128, 247, 3, 203, 2, 17, 0, 0, 0, 7, 51, 175, 153, 244, 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