Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 76928c5e70cf94e0c10b13710ecff3e9803ee773bbdc36cc283c7ae709a356c6

Tx prefix hash: 2c14302237111fc93d64ae36ec6a6c9e023e670e58967797add02ac4acc655ef
Tx public key: c34a3d7127cd594a0b99cad2bbbce102504fc66004a35f318e17fb4aab241d93
Timestamp: 1686113795 Timestamp [UCT]: 2023-06-07 04:56:35 Age [y:d:h:m:s]: 01:364:22:27:44
Block: 776867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 522055 RingCT/type: yes/0
Extra: 01c34a3d7127cd594a0b99cad2bbbce102504fc66004a35f318e17fb4aab241d93021100000004faf35c9c000000000000000000

1 output(s) for total of 1.636504862000 dcy

stealth address amount amount idx
00: 6d6f34f417bce306f78693b3ea41afaa8556197d5294e52325cba2d50fd0ae2e 1.636504862000 1226434 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": 776877, "vin": [ { "gen": { "height": 776867 } } ], "vout": [ { "amount": 1636504862, "target": { "key": "6d6f34f417bce306f78693b3ea41afaa8556197d5294e52325cba2d50fd0ae2e" } } ], "extra": [ 1, 195, 74, 61, 113, 39, 205, 89, 74, 11, 153, 202, 210, 187, 188, 225, 2, 80, 79, 198, 96, 4, 163, 95, 49, 142, 23, 251, 74, 171, 36, 29, 147, 2, 17, 0, 0, 0, 4, 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