Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bce251875c0f921de593bd3a8798737c687a054092c5601fb990d4d0e941a41b

Tx prefix hash: 08215b6d073ec502f55dc3a84b08e11f920a16f18a8e52a417839697c83f9475
Tx public key: f806002dda0d8910e1a0fc460d6adab2af6c10d5b7fb9117351217deacad45f3
Timestamp: 1713116373 Timestamp [UCT]: 2024-04-14 17:39:33 Age [y:d:h:m:s]: 00:362:03:35:40
Block: 1000463 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258938 RingCT/type: yes/0
Extra: 01f806002dda0d8910e1a0fc460d6adab2af6c10d5b7fb9117351217deacad45f302110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 304687892d2e4f008455573005c0578cb07e504f0769688b9709f0e1f7bce52d 0.600000000000 1460961 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": 1000473, "vin": [ { "gen": { "height": 1000463 } } ], "vout": [ { "amount": 600000000, "target": { "key": "304687892d2e4f008455573005c0578cb07e504f0769688b9709f0e1f7bce52d" } } ], "extra": [ 1, 248, 6, 0, 45, 218, 13, 137, 16, 225, 160, 252, 70, 13, 106, 218, 178, 175, 108, 16, 213, 183, 251, 145, 23, 53, 18, 23, 222, 172, 173, 69, 243, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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