Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6793a6befa5b134482ee33ffb17e276e1159f8d4047a07beb5998135d0a40ee9

Tx prefix hash: 675c434c316965bd9003dae7cce9c00a758853582a40f3088e71daa735bb2444
Tx public key: b43fb6d9dd7531a167e9249f3a2333dea4644cf02de40323ef5c10d6439f1f03
Timestamp: 1719192047 Timestamp [UCT]: 2024-06-24 01:20:47 Age [y:d:h:m:s]: 01:160:16:53:29
Block: 1050851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373432 RingCT/type: yes/0
Extra: 01b43fb6d9dd7531a167e9249f3a2333dea4644cf02de40323ef5c10d6439f1f0302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3e71147ae1fcebbe62d3b3146fdecb0b363fb4ca32a86d219301a5d9fa0b9c5 0.600000000000 1521026 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": 1050861, "vin": [ { "gen": { "height": 1050851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3e71147ae1fcebbe62d3b3146fdecb0b363fb4ca32a86d219301a5d9fa0b9c5" } } ], "extra": [ 1, 180, 63, 182, 217, 221, 117, 49, 161, 103, 233, 36, 159, 58, 35, 51, 222, 164, 100, 76, 240, 45, 228, 3, 35, 239, 92, 16, 214, 67, 159, 31, 3, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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