Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cb11b2108e31d8bd4a26e38c7c0f89fafda93318491d0215db03ee43d855744

Tx prefix hash: 57425c0783643922561d5343bd375d3d9133d15a2d7dce61eb3fee487f838f99
Tx public key: ae3aacc41c6a723dd1d2f44b5dd8f459f2baf00bad6d1859635cdc569b08f50a
Timestamp: 1734810485 Timestamp [UCT]: 2024-12-21 19:48:05 Age [y:d:h:m:s]: 00:097:23:55:25
Block: 1180255 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69795 RingCT/type: yes/0
Extra: 01ae3aacc41c6a723dd1d2f44b5dd8f459f2baf00bad6d1859635cdc569b08f50a0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f98694c0fd7f478f945829b043a93a027cf7711e9639551886037e8fb4a8a71d 0.600000000000 1666664 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": 1180265, "vin": [ { "gen": { "height": 1180255 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f98694c0fd7f478f945829b043a93a027cf7711e9639551886037e8fb4a8a71d" } } ], "extra": [ 1, 174, 58, 172, 196, 28, 106, 114, 61, 209, 210, 244, 75, 93, 216, 244, 89, 242, 186, 240, 11, 173, 109, 24, 89, 99, 92, 220, 86, 155, 8, 245, 10, 2, 17, 0, 0, 0, 1, 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