Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 252f6b40a22b004503eccad367969e386e5c59291f4afb91e04dbf243327addc

Tx prefix hash: 4224f18dbff65a13f470d84aedc39f31942116a8937c3b00b759742832a4a6b1
Tx public key: a3e9e4c87d401eff747f458980fc65b46e4153df14ea3d668d1589efc3c13c43
Timestamp: 1723332272 Timestamp [UCT]: 2024-08-10 23:24:32 Age [y:d:h:m:s]: 01:100:07:01:06
Block: 1085180 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330160 RingCT/type: yes/0
Extra: 01a3e9e4c87d401eff747f458980fc65b46e4153df14ea3d668d1589efc3c13c43021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce87525c2ea2d7460c693244fa2c139a469f315921c6e28e56b71e7a26b2ea8c 0.600000000000 1559709 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": 1085190, "vin": [ { "gen": { "height": 1085180 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce87525c2ea2d7460c693244fa2c139a469f315921c6e28e56b71e7a26b2ea8c" } } ], "extra": [ 1, 163, 233, 228, 200, 125, 64, 30, 255, 116, 127, 69, 137, 128, 252, 101, 180, 110, 65, 83, 223, 20, 234, 61, 102, 141, 21, 137, 239, 195, 193, 60, 67, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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