Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64ba10a35974d667fe554c3e61279be772d52e014bca35db735ba37d2d978d4f

Tx prefix hash: 270a3a6768562c2afec36c591a7b810311e922ac5cdeff93d979c650de415e35
Tx public key: 2242c1f9c9ea959b6277af73d1f6f6fbdec8fba394bed4a3d20b32cd849ffc95
Timestamp: 1722404857 Timestamp [UCT]: 2024-07-31 05:47:37 Age [y:d:h:m:s]: 00:116:17:28:53
Block: 1077492 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83516 RingCT/type: yes/0
Extra: 012242c1f9c9ea959b6277af73d1f6f6fbdec8fba394bed4a3d20b32cd849ffc950211000000038c7e50ca000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ba20285a3ba678207eaf475a0c8d2d9d57a6c69ab3e89810ecce9776d65f9724 0.600000000000 1550041 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": 1077502, "vin": [ { "gen": { "height": 1077492 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ba20285a3ba678207eaf475a0c8d2d9d57a6c69ab3e89810ecce9776d65f9724" } } ], "extra": [ 1, 34, 66, 193, 249, 201, 234, 149, 155, 98, 119, 175, 115, 209, 246, 246, 251, 222, 200, 251, 163, 148, 190, 212, 163, 210, 11, 50, 205, 132, 159, 252, 149, 2, 17, 0, 0, 0, 3, 140, 126, 80, 202, 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