Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a7dcb1f499889a7b04e94734e73c6a14003c2e69933c80f3d51d1fa3b0710517

Tx prefix hash: a41a3f5fb3f353ff620cc4e312d0d376367d1fa9cba264152f5dd346fbea5ee1
Tx public key: ab4c3de17d6fc158cbc08f46192579603284fb2a6c1153fa1a6baf17babb999c
Timestamp: 1578166578 Timestamp [UCT]: 2020-01-04 19:36:18 Age [y:d:h:m:s]: 05:164:05:03:35
Block: 38759 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1267137 RingCT/type: yes/0
Extra: 01ab4c3de17d6fc158cbc08f46192579603284fb2a6c1153fa1a6baf17babb999c02110000007d17786bcf000000000000000000

1 output(s) for total of 456.642356722000 dcy

stealth address amount amount idx
00: b710e222f43eb9c53b7f354fcd2e9af88b7b98251b78b8d5433f84c2baae021a 456.642356722000 66306 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": 38769, "vin": [ { "gen": { "height": 38759 } } ], "vout": [ { "amount": 456642356722, "target": { "key": "b710e222f43eb9c53b7f354fcd2e9af88b7b98251b78b8d5433f84c2baae021a" } } ], "extra": [ 1, 171, 76, 61, 225, 125, 111, 193, 88, 203, 192, 143, 70, 25, 37, 121, 96, 50, 132, 251, 42, 108, 17, 83, 250, 26, 107, 175, 23, 186, 187, 153, 156, 2, 17, 0, 0, 0, 125, 23, 120, 107, 207, 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