Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b76db9ac884a817c50270ecfcefdeddbb9056cffe6261ef427bcb11c3f8a4d6

Tx prefix hash: 41742194d76ed298bee3940ffdf529110dac5e749d509308e78685fb98148ee7
Tx public key: d947c7d06fd70b5399b7172a9c9da6b6d650a10248b158de7bea09cbd0a81a04
Timestamp: 1725290316 Timestamp [UCT]: 2024-09-02 15:18:36 Age [y:d:h:m:s]: 00:269:09:21:52
Block: 1101412 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192428 RingCT/type: yes/0
Extra: 01d947c7d06fd70b5399b7172a9c9da6b6d650a10248b158de7bea09cbd0a81a04021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 531db5d4517f215f1cf3a0b8d2b06be260474576d6167b216bd28f96823fca91 0.600000000000 1577453 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": 1101422, "vin": [ { "gen": { "height": 1101412 } } ], "vout": [ { "amount": 600000000, "target": { "key": "531db5d4517f215f1cf3a0b8d2b06be260474576d6167b216bd28f96823fca91" } } ], "extra": [ 1, 217, 71, 199, 208, 111, 215, 11, 83, 153, 183, 23, 42, 156, 157, 166, 182, 214, 80, 161, 2, 72, 177, 88, 222, 123, 234, 9, 203, 208, 168, 26, 4, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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