Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e17ddcca31c567e5333d3c9a148d2f63f716cc8da1c260f67b89c482dc06c8c2

Tx prefix hash: 5396fdcfe3ef63051055e1b962d3071e0ece57e67e07bd4c411bd0d15c4e8e5d
Tx public key: 47df38f2730cdf24f75f5f7f40cc6a271dd0b0b981cfc89d9747d03e4d7d3a2d
Timestamp: 1637444727 Timestamp [UCT]: 2021-11-20 21:45:27 Age [y:d:h:m:s]: 02:363:11:32:43
Block: 378551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 777745 RingCT/type: yes/0
Extra: 0147df38f2730cdf24f75f5f7f40cc6a271dd0b0b981cfc89d9747d03e4d7d3a2d0211000000031cab2639000000000000000000

1 output(s) for total of 34.174626426000 dcy

stealth address amount amount idx
00: 50117b7608f8de1490545ce6300f634ca0e42ead71099ad33fec6b3d4f7c5ddf 34.174626426000 765471 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": 378561, "vin": [ { "gen": { "height": 378551 } } ], "vout": [ { "amount": 34174626426, "target": { "key": "50117b7608f8de1490545ce6300f634ca0e42ead71099ad33fec6b3d4f7c5ddf" } } ], "extra": [ 1, 71, 223, 56, 242, 115, 12, 223, 36, 247, 95, 95, 127, 64, 204, 106, 39, 29, 208, 176, 185, 129, 207, 200, 157, 151, 71, 208, 62, 77, 125, 58, 45, 2, 17, 0, 0, 0, 3, 28, 171, 38, 57, 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