Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d6f079675f4a44e10adf8d1f3fccc5b6e46bcb9a710d668301b9ac33283dba3

Tx prefix hash: a2277781755a8a0eac660f6844a56fdcba7552c24becb087f4ec4d09263142c8
Tx public key: 36833d5c28d07458f5cd753d5257b0aa8cfa24a9f007f4a8f34260a1dad7a2ff
Timestamp: 1685465982 Timestamp [UCT]: 2023-05-30 16:59:42 Age [y:d:h:m:s]: 01:269:15:13:33
Block: 771507 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 453858 RingCT/type: yes/0
Extra: 0136833d5c28d07458f5cd753d5257b0aa8cfa24a9f007f4a8f34260a1dad7a2ff021100000003faf35c9c000000000000000000

1 output(s) for total of 1.704814823000 dcy

stealth address amount amount idx
00: 4dcd473aac5147ff494ae588434d437a7ca2eb69efc0d7c1040eb8d397723324 1.704814823000 1220876 of 0

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": 771517, "vin": [ { "gen": { "height": 771507 } } ], "vout": [ { "amount": 1704814823, "target": { "key": "4dcd473aac5147ff494ae588434d437a7ca2eb69efc0d7c1040eb8d397723324" } } ], "extra": [ 1, 54, 131, 61, 92, 40, 208, 116, 88, 245, 205, 117, 61, 82, 87, 176, 170, 140, 250, 36, 169, 240, 7, 244, 168, 243, 66, 96, 161, 218, 215, 162, 255, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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