Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 348ed9f0a899ceeee32c59f3e65e407ea93a38cad51879d597029523972c9b34

Tx prefix hash: 048d469c65750c2b46cc65def54b96fbb58679cde13d6fa900a3746fd729879d
Tx public key: d6b3c7d663a2e2cfa87805a73284f5b930dab1f2759e2f16f35dab9880cdbf93
Timestamp: 1705064071 Timestamp [UCT]: 2024-01-12 12:54:31 Age [y:d:h:m:s]: 01:075:20:48:45
Block: 933715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 315318 RingCT/type: yes/0
Extra: 01d6b3c7d663a2e2cfa87805a73284f5b930dab1f2759e2f16f35dab9880cdbf9302110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9b79f498f9e9421e4529da329a0667aed8820fe7f1b2227742dba5a8e7aeafe3 0.600000000000 1391685 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": 933725, "vin": [ { "gen": { "height": 933715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9b79f498f9e9421e4529da329a0667aed8820fe7f1b2227742dba5a8e7aeafe3" } } ], "extra": [ 1, 214, 179, 199, 214, 99, 162, 226, 207, 168, 120, 5, 167, 50, 132, 245, 185, 48, 218, 177, 242, 117, 158, 47, 22, 243, 93, 171, 152, 128, 205, 191, 147, 2, 17, 0, 0, 0, 5, 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