Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2100dbcf63f1ec514b9ac940ba17ae78f354f1b81a5307cc306c0e36f7625f7d

Tx prefix hash: 981170f5ecd2a0e4dd29fea3e4e7ca8b856ca4a64a4cd8428a1c46f90b0f253b
Tx public key: e34b64e87ae7ce513929d38ddf35cc26b0fa17315f38ae9f594672cce8edd48e
Timestamp: 1578864231 Timestamp [UCT]: 2020-01-12 21:23:51 Age [y:d:h:m:s]: 05:298:13:05:00
Block: 44201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1361226 RingCT/type: yes/0
Extra: 01e34b64e87ae7ce513929d38ddf35cc26b0fa17315f38ae9f594672cce8edd48e02110000000ad81c26c0000000000000000000

1 output(s) for total of 438.071076296000 dcy

stealth address amount amount idx
00: a759aa6956424cc79f1e9dbaaba45712a0425cc8a0b906ce37e46248291aade9 438.071076296000 80361 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": 44211, "vin": [ { "gen": { "height": 44201 } } ], "vout": [ { "amount": 438071076296, "target": { "key": "a759aa6956424cc79f1e9dbaaba45712a0425cc8a0b906ce37e46248291aade9" } } ], "extra": [ 1, 227, 75, 100, 232, 122, 231, 206, 81, 57, 41, 211, 141, 223, 53, 204, 38, 176, 250, 23, 49, 95, 56, 174, 159, 89, 70, 114, 204, 232, 237, 212, 142, 2, 17, 0, 0, 0, 10, 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