Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a1a023d47f77f331b7411a86c52106922c6c4fabd8c9704fc66df765a7472847

Tx prefix hash: c3c4f844e402049fd3dd59e65a14d1d82bf9d2b1db8f9fcd8c90116b8e15a3bc
Tx public key: 323a4b8d338b136bb9d655a678d9cbb1e001a3f526f12b13324550f039349576
Timestamp: 1707034192 Timestamp [UCT]: 2024-02-04 08:09:52 Age [y:d:h:m:s]: 00:347:00:02:35
Block: 950051 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248414 RingCT/type: yes/0
Extra: 01323a4b8d338b136bb9d655a678d9cbb1e001a3f526f12b13324550f03934957602110000000510a1748f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 388bea82c4ed2cd64fa3d8fa206b3f99963f64d92f30a7dd61e7a94cc9773c09 0.600000000000 1408609 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": 950061, "vin": [ { "gen": { "height": 950051 } } ], "vout": [ { "amount": 600000000, "target": { "key": "388bea82c4ed2cd64fa3d8fa206b3f99963f64d92f30a7dd61e7a94cc9773c09" } } ], "extra": [ 1, 50, 58, 75, 141, 51, 139, 19, 107, 185, 214, 85, 166, 120, 217, 203, 177, 224, 1, 163, 245, 38, 241, 43, 19, 50, 69, 80, 240, 57, 52, 149, 118, 2, 17, 0, 0, 0, 5, 16, 161, 116, 143, 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