Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0719ad4bfdce3947da6443a0aff58a6cd57497a4bac340845ed7726da416843

Tx prefix hash: d1821bb4bd10f0e5471056306e5a8d8b8977ffcdade48123f40e4832a0f8813e
Tx public key: 1f845816a5b88be53cfe517ccec5b213c69c4be0b82f47ff83d665d5df7ae191
Timestamp: 1699131352 Timestamp [UCT]: 2023-11-04 20:55:52 Age [y:d:h:m:s]: 01:223:21:29:46
Block: 884799 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 420909 RingCT/type: yes/0
Extra: 011f845816a5b88be53cfe517ccec5b213c69c4be0b82f47ff83d665d5df7ae191021100000001faf35c9c000000000000000000

1 output(s) for total of 0.718279747000 dcy

stealth address amount amount idx
00: 9128b6f2a0e6a97e8f7e7fd42b0e34ae7d820d63f8b49fae6a15d823b620f5e9 0.718279747000 1340546 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": 884809, "vin": [ { "gen": { "height": 884799 } } ], "vout": [ { "amount": 718279747, "target": { "key": "9128b6f2a0e6a97e8f7e7fd42b0e34ae7d820d63f8b49fae6a15d823b620f5e9" } } ], "extra": [ 1, 31, 132, 88, 22, 165, 184, 139, 229, 60, 254, 81, 124, 206, 197, 178, 19, 198, 156, 75, 224, 184, 47, 71, 255, 131, 214, 101, 213, 223, 122, 225, 145, 2, 17, 0, 0, 0, 1, 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