Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5f5c9dc3caec0f9bc432ef243ca23883271ae0bc03d3b1bb795d3aeba890810

Tx prefix hash: d88fcf5e8179580dbf2ea6b4e8156ce171f867e401bd01b51f905c3cc066af95
Tx public key: 689d9ba25883a877ac57d60abe4b4646586daa8f29fdf9e2fea09c9007343571
Timestamp: 1730940556 Timestamp [UCT]: 2024-11-07 00:49:16 Age [y:d:h:m:s]: 00:017:06:48:18
Block: 1148169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 12375 RingCT/type: yes/0
Extra: 01689d9ba25883a877ac57d60abe4b4646586daa8f29fdf9e2fea09c90073435710211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4bd3b43fc42430ba283661b62c36391c3f4a1ec9389c2b02696605d7eaa2d0f 0.600000000000 1632954 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": 1148179, "vin": [ { "gen": { "height": 1148169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4bd3b43fc42430ba283661b62c36391c3f4a1ec9389c2b02696605d7eaa2d0f" } } ], "extra": [ 1, 104, 157, 155, 162, 88, 131, 168, 119, 172, 87, 214, 10, 190, 75, 70, 70, 88, 109, 170, 143, 41, 253, 249, 226, 254, 160, 156, 144, 7, 52, 53, 113, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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