Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bf971dc9bc0cd4cb033d29e7e1e32df50b01c991fb06a91b6e5c4e8dafd37a7c

Tx prefix hash: a4a85d260bfee2a772b88614e01d683218edaf353b56b80fbe76b32c7f58dd42
Tx public key: f4471bc469e1b60c043b14fe035b5af9f9b5dcf0dfff7d403c69868c36a99ec0
Timestamp: 1731503296 Timestamp [UCT]: 2024-11-13 13:08:16 Age [y:d:h:m:s]: 00:221:20:49:02
Block: 1152838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158220 RingCT/type: yes/0
Extra: 01f4471bc469e1b60c043b14fe035b5af9f9b5dcf0dfff7d403c69868c36a99ec00211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc1d74d5e67dcee505534551fa8ec63d300b8c8e13f9163bbddcadd63afcd8dd 0.600000000000 1638443 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": 1152848, "vin": [ { "gen": { "height": 1152838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc1d74d5e67dcee505534551fa8ec63d300b8c8e13f9163bbddcadd63afcd8dd" } } ], "extra": [ 1, 244, 71, 27, 196, 105, 225, 182, 12, 4, 59, 20, 254, 3, 91, 90, 249, 249, 181, 220, 240, 223, 255, 125, 64, 60, 105, 134, 140, 54, 169, 158, 192, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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