Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a9abb5e8553242131ed3d0be895ebac95cac63ee9b40f11d62c161ffedaf2e1

Tx prefix hash: a35d352142dc40e6293c5df1871062b95b80b26ed287b5073abfa1fd070bc1de
Tx public key: a53aff86c9654f7f96dc401b9a45f6f24b238091b6446fd3815b12c276e6a955
Timestamp: 1725044612 Timestamp [UCT]: 2024-08-30 19:03:32 Age [y:d:h:m:s]: 00:229:08:58:15
Block: 1099370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163797 RingCT/type: yes/0
Extra: 01a53aff86c9654f7f96dc401b9a45f6f24b238091b6446fd3815b12c276e6a95502110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca80335ff96a4992f2d6307ed3638504b2705f7e58483e4c27c6bcd795ebaafe 0.600000000000 1575331 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": 1099380, "vin": [ { "gen": { "height": 1099370 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca80335ff96a4992f2d6307ed3638504b2705f7e58483e4c27c6bcd795ebaafe" } } ], "extra": [ 1, 165, 58, 255, 134, 201, 101, 79, 127, 150, 220, 64, 27, 154, 69, 246, 242, 75, 35, 128, 145, 182, 68, 111, 211, 129, 91, 18, 194, 118, 230, 169, 85, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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