Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58d3fe9c7f847c73670a0469cd33649a3a76b8094e4dbf3cbb9586592edb0351

Tx prefix hash: 4b9ef0ef45d2a791a1659c5634b860932537cc41d6fd7ad22d7f96c00c75bd5c
Tx public key: 52fe6c987edb15e7341de5c6a5cf78dfd5ad32b710d74d85f4ab2644231300dd
Timestamp: 1712777228 Timestamp [UCT]: 2024-04-10 19:27:08 Age [y:d:h:m:s]: 00:363:17:01:51
Block: 997651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 260053 RingCT/type: yes/0
Extra: 0152fe6c987edb15e7341de5c6a5cf78dfd5ad32b710d74d85f4ab2644231300dd02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7bf5633e83756baef271506ee11dcdf0eef969b0c9cb9be30e9f222e0110a7ca 0.600000000000 1458085 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": 997661, "vin": [ { "gen": { "height": 997651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7bf5633e83756baef271506ee11dcdf0eef969b0c9cb9be30e9f222e0110a7ca" } } ], "extra": [ 1, 82, 254, 108, 152, 126, 219, 21, 231, 52, 29, 229, 198, 165, 207, 120, 223, 213, 173, 50, 183, 16, 215, 77, 133, 244, 171, 38, 68, 35, 19, 0, 221, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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