Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c456b08784c4ffff4b797a8d21d340e84a83ea773e2087b5dc1a689d9c2924f

Tx prefix hash: 29bf42597affd156d0e0c2f5dc20186789f0f61f589fba824506f68b27060402
Tx public key: 78bbabacc79cfa89b99a06b56d2f430b16510ec5e63ebae71251ee1210478cdd
Timestamp: 1677690348 Timestamp [UCT]: 2023-03-01 17:05:48 Age [y:d:h:m:s]: 01:078:20:32:23
Block: 707667 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317062 RingCT/type: yes/0
Extra: 0178bbabacc79cfa89b99a06b56d2f430b16510ec5e63ebae71251ee1210478cdd0211000000035029cbac000000000000000000

1 output(s) for total of 2.774631833000 dcy

stealth address amount amount idx
00: f5a9a01ae4aafb93cf1f188672e32f5ca1ebba851fa2bdd798ef8fa7d6e0dcb6 2.774631833000 1151486 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": 707677, "vin": [ { "gen": { "height": 707667 } } ], "vout": [ { "amount": 2774631833, "target": { "key": "f5a9a01ae4aafb93cf1f188672e32f5ca1ebba851fa2bdd798ef8fa7d6e0dcb6" } } ], "extra": [ 1, 120, 187, 171, 172, 199, 156, 250, 137, 185, 154, 6, 181, 109, 47, 67, 11, 22, 81, 14, 197, 230, 62, 186, 231, 18, 81, 238, 18, 16, 71, 140, 221, 2, 17, 0, 0, 0, 3, 80, 41, 203, 172, 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