Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 237d512a65dd8b10d2e7b7bc5b95b4b60dcc5b54ffbd6f5cea91720d071bdc6a

Tx prefix hash: 864f1d7101fe58dd3f45ca00a9536572d6a5575369c3aea8f3af8b3e74343b4b
Tx public key: af54bead0a3b90d8d063d06ea41b9777ef9dece1eef8dfbfbe3dc775267149fe
Timestamp: 1634071526 Timestamp [UCT]: 2021-10-12 20:45:26 Age [y:d:h:m:s]: 03:026:22:15:34
Block: 351878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 796842 RingCT/type: yes/0
Extra: 01af54bead0a3b90d8d063d06ea41b9777ef9dece1eef8dfbfbe3dc775267149fe02110000004836fe6557000000000000000000

1 output(s) for total of 41.889006152000 dcy

stealth address amount amount idx
00: 3971734e1f6ea57dbc9f2947f1fe954ac906143629635230e9c8f3b715b20369 41.889006152000 719426 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": 351888, "vin": [ { "gen": { "height": 351878 } } ], "vout": [ { "amount": 41889006152, "target": { "key": "3971734e1f6ea57dbc9f2947f1fe954ac906143629635230e9c8f3b715b20369" } } ], "extra": [ 1, 175, 84, 190, 173, 10, 59, 144, 216, 208, 99, 208, 110, 164, 27, 151, 119, 239, 157, 236, 225, 238, 248, 223, 191, 190, 61, 199, 117, 38, 113, 73, 254, 2, 17, 0, 0, 0, 72, 54, 254, 101, 87, 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