Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 019f9416d0390b298c2ccb78786e15f2932e671c7647f762f1e38c96798fa1e6

Tx prefix hash: 4986e0e3150cad82dd030bcda9ca1b0f38aabf76be8560b9cbb6f0141ce8f09a
Tx public key: 2c9b3fd1ea77fddad2bd5783548f370e5397c65b3bcb1e0201b7e78fee9a77a0
Timestamp: 1718658339 Timestamp [UCT]: 2024-06-17 21:05:39 Age [y:d:h:m:s]: 00:218:23:51:13
Block: 1046433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156666 RingCT/type: yes/0
Extra: 012c9b3fd1ea77fddad2bd5783548f370e5397c65b3bcb1e0201b7e78fee9a77a002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47e4808312a8682fc70922ca84d688f25a1362cd1b05ca20cfb5d7504efde8a9 0.600000000000 1516246 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": 1046443, "vin": [ { "gen": { "height": 1046433 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47e4808312a8682fc70922ca84d688f25a1362cd1b05ca20cfb5d7504efde8a9" } } ], "extra": [ 1, 44, 155, 63, 209, 234, 119, 253, 218, 210, 189, 87, 131, 84, 143, 55, 14, 83, 151, 198, 91, 59, 203, 30, 2, 1, 183, 231, 143, 238, 154, 119, 160, 2, 17, 0, 0, 0, 7, 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