Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 169ae9d352462c76182db6383e53a0e2fb4621bc1b8864de5569fe0bf355e6db

Tx prefix hash: 388d5244df570765c6b4d3fd748e4ca00e98329a6e9f36292df47f47eb56fb58
Tx public key: 8c501804a72b810d98b776f4cda13cc29e016457765a55fbcf1bd6eefa09de4e
Timestamp: 1583532016 Timestamp [UCT]: 2020-03-06 22:00:16 Age [y:d:h:m:s]: 05:042:08:09:20
Block: 77704 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1185531 RingCT/type: yes/0
Extra: 018c501804a72b810d98b776f4cda13cc29e016457765a55fbcf1bd6eefa09de4e02110000001a8a2ee0d9000000000000000000

1 output(s) for total of 339.261974111000 dcy

stealth address amount amount idx
00: f381d7a5ae34d0db9ba0d745e2dc615e94ace826bf83bc3f6b92eddbb98ea2df 339.261974111000 142871 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": 77714, "vin": [ { "gen": { "height": 77704 } } ], "vout": [ { "amount": 339261974111, "target": { "key": "f381d7a5ae34d0db9ba0d745e2dc615e94ace826bf83bc3f6b92eddbb98ea2df" } } ], "extra": [ 1, 140, 80, 24, 4, 167, 43, 129, 13, 152, 183, 118, 244, 205, 161, 60, 194, 158, 1, 100, 87, 118, 90, 85, 251, 207, 27, 214, 238, 250, 9, 222, 78, 2, 17, 0, 0, 0, 26, 138, 46, 224, 217, 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