Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d8c954b9e66fe7aa26edd1ba7e7942c8a34cd58f40dfbf22a670bf3547552f17

Tx prefix hash: 79fdddc09e1dbea8faa42d2667a85dd80cdb00657a28f819b389e204259d813c
Tx public key: 566cdf2cce5f434e0ddcf1378ad6f8b01ff228c017307f1e6e671800d683f69d
Timestamp: 1734358350 Timestamp [UCT]: 2024-12-16 14:12:30 Age [y:d:h:m:s]: 00:123:20:42:11
Block: 1176502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88295 RingCT/type: yes/0
Extra: 01566cdf2cce5f434e0ddcf1378ad6f8b01ff228c017307f1e6e671800d683f69d021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6b5ab7fd5fb4c2c2570c9f5dc3292eca8c96b1aa6fdd348620cd23836f29d73 0.600000000000 1662843 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": 1176512, "vin": [ { "gen": { "height": 1176502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6b5ab7fd5fb4c2c2570c9f5dc3292eca8c96b1aa6fdd348620cd23836f29d73" } } ], "extra": [ 1, 86, 108, 223, 44, 206, 95, 67, 78, 13, 220, 241, 55, 138, 214, 248, 176, 31, 242, 40, 192, 23, 48, 127, 30, 110, 103, 24, 0, 214, 131, 246, 157, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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