Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d297f42e4637248bfd5307200250991b6bc04112e48f40e9e2617a4129cb414c

Tx prefix hash: 376a2d677c7b0f3dc2f8c66cc29df52653c490cf2adbef7f0250e9142af52e98
Tx public key: 2a2d4f23ced112d52c80b0642f9475bf3aa8cc76ce99b8d2a3fe95556ffc0b6f
Timestamp: 1712134942 Timestamp [UCT]: 2024-04-03 09:02:22 Age [y:d:h:m:s]: 01:243:00:54:14
Block: 992317 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432445 RingCT/type: yes/0
Extra: 012a2d4f23ced112d52c80b0642f9475bf3aa8cc76ce99b8d2a3fe95556ffc0b6f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53757db6c32f54520919e85291357fc99af3b0e154c6f318121300448a4c65b3 0.600000000000 1452657 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": 992327, "vin": [ { "gen": { "height": 992317 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53757db6c32f54520919e85291357fc99af3b0e154c6f318121300448a4c65b3" } } ], "extra": [ 1, 42, 45, 79, 35, 206, 209, 18, 213, 44, 128, 176, 100, 47, 148, 117, 191, 58, 168, 204, 118, 206, 153, 184, 210, 163, 254, 149, 85, 111, 252, 11, 111, 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