Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53a925e340eec8789a5c2c1a0413ba476ad0b458b3e9f55b70293e315601eb59

Tx prefix hash: 2c1c8e091447f2a0866f2dd7531c717269b20ce3cb3b7f84c722f8f70e2b6050
Tx public key: aa489a572959b8e8ee8f1dae68a28664ef40f47dcec620ebf750c6a3c14f7116
Timestamp: 1602853667 Timestamp [UCT]: 2020-10-16 13:07:47 Age [y:d:h:m:s]: 04:192:19:07:24
Block: 141347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1128387 RingCT/type: yes/0
Extra: 01aa489a572959b8e8ee8f1dae68a28664ef40f47dcec620ebf750c6a3c14f7116021100000006f8cbd8e0000000000000000000

1 output(s) for total of 208.765829993000 dcy

stealth address amount amount idx
00: cf64b2a9de2245e3b2497e912dc67138fd8f25d2a5528a15018c8a69a9b7fb4c 208.765829993000 234881 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": 141357, "vin": [ { "gen": { "height": 141347 } } ], "vout": [ { "amount": 208765829993, "target": { "key": "cf64b2a9de2245e3b2497e912dc67138fd8f25d2a5528a15018c8a69a9b7fb4c" } } ], "extra": [ 1, 170, 72, 154, 87, 41, 89, 184, 232, 238, 143, 29, 174, 104, 162, 134, 100, 239, 64, 244, 125, 206, 198, 32, 235, 247, 80, 198, 163, 193, 79, 113, 22, 2, 17, 0, 0, 0, 6, 248, 203, 216, 224, 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