Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14d47d2c7f44dd2a8dae939f6fcc8f448297f2e69622bc58ba45fe9d8a5b1311

Tx prefix hash: 76b554b2324540e9c33318807ca97eb5de65b08850ceb7810881d0495afda082
Tx public key: b3d3948a6381565f48911d058532f89b63eec59f37d4f1a74b4c64fbe2dbf0cf
Timestamp: 1581959433 Timestamp [UCT]: 2020-02-17 17:10:33 Age [y:d:h:m:s]: 04:286:18:35:44
Block: 66987 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1097262 RingCT/type: yes/0
Extra: 01b3d3948a6381565f48911d058532f89b63eec59f37d4f1a74b4c64fbe2dbf0cf021100000021d81c26c0000000000000000000

1 output(s) for total of 368.167178682000 dcy

stealth address amount amount idx
00: b69aa01083bf07d306c4922081089ef7cf1ddd534636e4b3d2c78adcde18cdcc 368.167178682000 123336 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": 66997, "vin": [ { "gen": { "height": 66987 } } ], "vout": [ { "amount": 368167178682, "target": { "key": "b69aa01083bf07d306c4922081089ef7cf1ddd534636e4b3d2c78adcde18cdcc" } } ], "extra": [ 1, 179, 211, 148, 138, 99, 129, 86, 95, 72, 145, 29, 5, 133, 50, 248, 155, 99, 238, 197, 159, 55, 212, 241, 167, 75, 76, 100, 251, 226, 219, 240, 207, 2, 17, 0, 0, 0, 33, 216, 28, 38, 192, 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