Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 011c984472061ac0269b81299c980a028bcfb6aab2632266c26e5c8cdacfd6ee

Tx prefix hash: 733bff73329fcc2e03169f2b1da13ede5588c75e0f936d0efc19916b48d963e0
Tx public key: a28fe5ba9959ebef2fcb56774717caa682b56ce0fb6623aa14cc02aa51a0db31
Timestamp: 1629181964 Timestamp [UCT]: 2021-08-17 06:32:44 Age [y:d:h:m:s]: 03:107:03:38:00
Block: 315793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 849844 RingCT/type: yes/0
Extra: 01a28fe5ba9959ebef2fcb56774717caa682b56ce0fb6623aa14cc02aa51a0db3102110000000bb75ebe6a000000000000000000

1 output(s) for total of 55.162909755000 dcy

stealth address amount amount idx
00: 3cca7a0666f7310288fbea1c145140a219edc3e8d25d49008946fc94c4d168f3 55.162909755000 657150 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": 315803, "vin": [ { "gen": { "height": 315793 } } ], "vout": [ { "amount": 55162909755, "target": { "key": "3cca7a0666f7310288fbea1c145140a219edc3e8d25d49008946fc94c4d168f3" } } ], "extra": [ 1, 162, 143, 229, 186, 153, 89, 235, 239, 47, 203, 86, 119, 71, 23, 202, 166, 130, 181, 108, 224, 251, 102, 35, 170, 20, 204, 2, 170, 81, 160, 219, 49, 2, 17, 0, 0, 0, 11, 183, 94, 190, 106, 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