Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9165b3d7515f2d258aab3a86e43ded9a97e72bc5046cff4ceca76575a405872

Tx prefix hash: 47467884426fc4b12b1051ac93f90b2a897eb20faf1da2a1911458896870188e
Tx public key: 81040a7e2bddf5d6364003132a02d0c6888ac0d1d9074512f941b9f20cbfc9eb
Timestamp: 1631743522 Timestamp [UCT]: 2021-09-15 22:05:22 Age [y:d:h:m:s]: 03:140:21:47:06
Block: 334554 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 876151 RingCT/type: yes/0
Extra: 0181040a7e2bddf5d6364003132a02d0c6888ac0d1d9074512f941b9f20cbfc9eb021100000014fdc024ec000000000000000000

1 output(s) for total of 47.806192719000 dcy

stealth address amount amount idx
00: e05b835eda5586095e57b277d8306fe16ef4a66c43be97a6402e35b7c7d5bc8b 47.806192719000 690011 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": 334564, "vin": [ { "gen": { "height": 334554 } } ], "vout": [ { "amount": 47806192719, "target": { "key": "e05b835eda5586095e57b277d8306fe16ef4a66c43be97a6402e35b7c7d5bc8b" } } ], "extra": [ 1, 129, 4, 10, 126, 43, 221, 245, 214, 54, 64, 3, 19, 42, 2, 208, 198, 136, 138, 192, 209, 217, 7, 69, 18, 249, 65, 185, 242, 12, 191, 201, 235, 2, 17, 0, 0, 0, 20, 253, 192, 36, 236, 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