Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acd684a316dac70fe4f4beb21464a90f9c8017fc258ef4415af3f0068a14b032

Tx prefix hash: c45a5d1633c1cae45d620f6ad7add044cddb80fb6e3fe329766482b65d873242
Tx public key: de7d2d1c010809efe2d73d41ed444b17261a568c1fecfbcf24f290176d2f9f9a
Timestamp: 1711506015 Timestamp [UCT]: 2024-03-27 02:20:15 Age [y:d:h:m:s]: 01:054:11:13:32
Block: 987165 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299906 RingCT/type: yes/0
Extra: 01de7d2d1c010809efe2d73d41ed444b17261a568c1fecfbcf24f290176d2f9f9a0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 117f4cc0671b5d9992649aa009d9e0b7b766ef82e4e61508bea1fb9190025965 0.600000000000 1447406 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": 987175, "vin": [ { "gen": { "height": 987165 } } ], "vout": [ { "amount": 600000000, "target": { "key": "117f4cc0671b5d9992649aa009d9e0b7b766ef82e4e61508bea1fb9190025965" } } ], "extra": [ 1, 222, 125, 45, 28, 1, 8, 9, 239, 226, 215, 61, 65, 237, 68, 75, 23, 38, 26, 86, 140, 31, 236, 251, 207, 36, 242, 144, 23, 109, 47, 159, 154, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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