Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0a673929b8645b11e9d60aa04b41b451e210b5694b4f214f67836a7a18c686df

Tx prefix hash: d14c4875431df69328fa2a104aa0517e563fed02a7102ec4c71824bf2c6bd8c4
Tx public key: 02020f92c1e94a6cccda580b980978546719bf33df4bd7a69c76e8cb156c79f4
Timestamp: 1731382678 Timestamp [UCT]: 2024-11-12 03:37:58 Age [y:d:h:m:s]: 00:211:21:57:53
Block: 1151827 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151302 RingCT/type: yes/0
Extra: 0102020f92c1e94a6cccda580b980978546719bf33df4bd7a69c76e8cb156c79f40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5aa349a42d81c128e545eb53a1603790f50558af23a7186e8f0026c76edd68f5 0.600000000000 1637410 of 15

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": 1151837, "vin": [ { "gen": { "height": 1151827 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5aa349a42d81c128e545eb53a1603790f50558af23a7186e8f0026c76edd68f5" } } ], "extra": [ 1, 2, 2, 15, 146, 193, 233, 74, 108, 204, 218, 88, 11, 152, 9, 120, 84, 103, 25, 191, 51, 223, 75, 215, 166, 156, 118, 232, 203, 21, 108, 121, 244, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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