Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80469dc8c314ac7ba1afcd7a29db3c3f3bab54f8f47df0ca516ff838b9735654

Tx prefix hash: 3f0b3f5b137b9531a815fbef23bc061d69369d3464fd0964e3bed4cad9add08c
Tx public key: 17a9cf724ddc1b517e49d15c0412b25ff537d88e82264153cad5381dd859bc6e
Timestamp: 1725326013 Timestamp [UCT]: 2024-09-03 01:13:33 Age [y:d:h:m:s]: 00:286:01:39:58
Block: 1101715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204254 RingCT/type: yes/0
Extra: 0117a9cf724ddc1b517e49d15c0412b25ff537d88e82264153cad5381dd859bc6e02110000001ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8569ce8d6e0481eb4e535f6c08b2825b7873ea1bbe6d1f13a9fab1650ea24e74 0.600000000000 1577870 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": 1101725, "vin": [ { "gen": { "height": 1101715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8569ce8d6e0481eb4e535f6c08b2825b7873ea1bbe6d1f13a9fab1650ea24e74" } } ], "extra": [ 1, 23, 169, 207, 114, 77, 220, 27, 81, 126, 73, 209, 92, 4, 18, 178, 95, 245, 55, 216, 142, 130, 38, 65, 83, 202, 213, 56, 29, 216, 89, 188, 110, 2, 17, 0, 0, 0, 26, 233, 20, 221, 21, 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