Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c3e4ab60797d118f9aff920f806512783f1405fbd81c8185edec1f29efa1ebe

Tx prefix hash: 18d973f2aed76b35c04730d0a1de9791d304ec04b1c3d4e72302df1b2a1c0244
Tx public key: 7c2a5f50ebda59e7eb08f8bda80f05fafa3e2c163b8939cdac854238afb50752
Timestamp: 1708637279 Timestamp [UCT]: 2024-02-22 21:27:59 Age [y:d:h:m:s]: 01:084:10:36:24
Block: 963351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 321403 RingCT/type: yes/0
Extra: 017c2a5f50ebda59e7eb08f8bda80f05fafa3e2c163b8939cdac854238afb5075202110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5f6237911d798da5264c8b4e3f14faa015f043f5d1e554b303f015112ba6586c 0.600000000000 1423052 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": 963361, "vin": [ { "gen": { "height": 963351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5f6237911d798da5264c8b4e3f14faa015f043f5d1e554b303f015112ba6586c" } } ], "extra": [ 1, 124, 42, 95, 80, 235, 218, 89, 231, 235, 8, 248, 189, 168, 15, 5, 250, 250, 62, 44, 22, 59, 137, 57, 205, 172, 133, 66, 56, 175, 181, 7, 82, 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