Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7a54b8c0f632845375c89445101d803629aa5fc8bb0b95e9d8e4db79a3a5b48f

Tx prefix hash: 01ab17136ad8a2f0fbfea4c1ccc33e23323107c827fbd9b5ea2c784222d07ba5
Tx public key: 96c6eb46631e6538525aea67829edcb64f54d1bf06f321377121daadca80d4d7
Timestamp: 1584922512 Timestamp [UCT]: 2020-03-23 00:15:12 Age [y:d:h:m:s]: 04:279:00:22:33
Block: 86906 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1096323 RingCT/type: yes/0
Extra: 0196c6eb46631e6538525aea67829edcb64f54d1bf06f321377121daadca80d4d7021100000097c2c2f844000000000000000000

1 output(s) for total of 316.260625416000 dcy

stealth address amount amount idx
00: c659057b91b6ffa323df813e317d7de4a58e635495ddbd8a629204f80b011fd5 316.260625416000 156740 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": 86916, "vin": [ { "gen": { "height": 86906 } } ], "vout": [ { "amount": 316260625416, "target": { "key": "c659057b91b6ffa323df813e317d7de4a58e635495ddbd8a629204f80b011fd5" } } ], "extra": [ 1, 150, 198, 235, 70, 99, 30, 101, 56, 82, 90, 234, 103, 130, 158, 220, 182, 79, 84, 209, 191, 6, 243, 33, 55, 113, 33, 218, 173, 202, 128, 212, 215, 2, 17, 0, 0, 0, 151, 194, 194, 248, 68, 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