Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f2552fbd603a4c2545fb7cee797254896ca185d323014e13541ac29a8110df3

Tx prefix hash: fc7545e349ab92304ee76267af96552633d86444aafb6f2eebb6cf0c822f7bd1
Tx public key: 7c87d0d8778d692153fb8cb63253f44dbd5dfecb48436bfc0da7af12261b971a
Timestamp: 1574656808 Timestamp [UCT]: 2019-11-25 04:40:08 Age [y:d:h:m:s]: 05:036:12:29:03
Block: 16915 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1168950 RingCT/type: yes/0
Extra: 017c87d0d8778d692153fb8cb63253f44dbd5dfecb48436bfc0da7af12261b971a021100000001f95225a5000000000000000000

1 output(s) for total of 539.466008258000 dcy

stealth address amount amount idx
00: d36080d07f082f217f0d2440d875213f7a3152b53004c9bfd8e9e69516bb1a1b 539.466008258000 24071 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": 16925, "vin": [ { "gen": { "height": 16915 } } ], "vout": [ { "amount": 539466008258, "target": { "key": "d36080d07f082f217f0d2440d875213f7a3152b53004c9bfd8e9e69516bb1a1b" } } ], "extra": [ 1, 124, 135, 208, 216, 119, 141, 105, 33, 83, 251, 140, 182, 50, 83, 244, 77, 189, 93, 254, 203, 72, 67, 107, 252, 13, 167, 175, 18, 38, 27, 151, 26, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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