Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c0c3b9b4bb5ffb24bf57d4bb4f9e75d132fc8f9ccea4bd44643a364a155e3ee

Tx prefix hash: b8bc2af21277a8fc9f250f73f97f07d30ed118ab32a8342454f4ddecdc965246
Tx public key: 296e5cc85b3313a1f7135aba3361b4d6fbbfbfa5aa0be9184081a36575b8345b
Timestamp: 1655745061 Timestamp [UCT]: 2022-06-20 17:11:01 Age [y:d:h:m:s]: 03:157:09:11:28
Block: 526672 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 892127 RingCT/type: yes/0
Extra: 01296e5cc85b3313a1f7135aba3361b4d6fbbfbfa5aa0be9184081a36575b8345b0211000000672e6b1fd5000000000000000000

1 output(s) for total of 11.038681391000 dcy

stealth address amount amount idx
00: 5e8f60aa23eb3e711d9b2bb4df6cc425ca1fc8eaa3cf731d97f6926f32b91e6c 11.038681391000 955235 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": 526682, "vin": [ { "gen": { "height": 526672 } } ], "vout": [ { "amount": 11038681391, "target": { "key": "5e8f60aa23eb3e711d9b2bb4df6cc425ca1fc8eaa3cf731d97f6926f32b91e6c" } } ], "extra": [ 1, 41, 110, 92, 200, 91, 51, 19, 161, 247, 19, 90, 186, 51, 97, 180, 214, 251, 191, 191, 165, 170, 11, 233, 24, 64, 129, 163, 101, 117, 184, 52, 91, 2, 17, 0, 0, 0, 103, 46, 107, 31, 213, 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