Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf5fe572f032a43dc2ee3bd32028ad54336aa434f4d7f06cfd29a9f619faedc5

Tx prefix hash: 739d4d87a76d24ce606c56a4064314e27087c6f470a06fbeaa551e1d1964a52b
Tx public key: 730ba5a442e80173b8b57f170a753d3c9beced3bff5dac393c369f69bd624bcb
Timestamp: 1711277939 Timestamp [UCT]: 2024-03-24 10:58:59 Age [y:d:h:m:s]: 00:181:03:20:01
Block: 985264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129734 RingCT/type: yes/0
Extra: 01730ba5a442e80173b8b57f170a753d3c9beced3bff5dac393c369f69bd624bcb02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 88760dc42c1d1c0e901fef4dcb5c281f75a3634d48ffea71afa71eeb1334ab2b 0.600000000000 1445473 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": 985274, "vin": [ { "gen": { "height": 985264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "88760dc42c1d1c0e901fef4dcb5c281f75a3634d48ffea71afa71eeb1334ab2b" } } ], "extra": [ 1, 115, 11, 165, 164, 66, 232, 1, 115, 184, 181, 127, 23, 10, 117, 61, 60, 155, 236, 237, 59, 255, 93, 172, 57, 60, 54, 159, 105, 189, 98, 75, 203, 2, 17, 0, 0, 0, 5, 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