Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d84dd2717513eb86b4f2fcd3cf287abb862d2dccf734a04a8284ef6c56065f9

Tx prefix hash: 41956a236afcf1ea7f39efa500435efdf780f312dbb3b75c2276c1a712f8e8c5
Tx public key: 4181f2b668ce92d74972c455e42b9abec53cdfd72155e24cdf874c2ef9c32171
Timestamp: 1703899880 Timestamp [UCT]: 2023-12-30 01:31:20 Age [y:d:h:m:s]: 01:320:07:19:10
Block: 924073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 487767 RingCT/type: yes/0
Extra: 014181f2b668ce92d74972c455e42b9abec53cdfd72155e24cdf874c2ef9c321710211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb98741df09dc4e29fae3a3de1df36a147cbe0dae31425f276e0edb58da4fa24 0.600000000000 1381815 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": 924083, "vin": [ { "gen": { "height": 924073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb98741df09dc4e29fae3a3de1df36a147cbe0dae31425f276e0edb58da4fa24" } } ], "extra": [ 1, 65, 129, 242, 182, 104, 206, 146, 215, 73, 114, 196, 85, 228, 43, 154, 190, 197, 60, 223, 215, 33, 85, 226, 76, 223, 135, 76, 46, 249, 195, 33, 113, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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