Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95c43cce703a4e38618281745810f5d42b9073ea5d9bdbd27dd6458ea176040

Tx prefix hash: 88a810b601db10e5fcf9d96a782921c01a8ef13bc01496a54da233b68cbe1edf
Tx public key: 59e60d0a61523a9d9b070be48abeb15ab3e1c99424fd3c2ef811447e5647b704
Timestamp: 1715203521 Timestamp [UCT]: 2024-05-08 21:25:21 Age [y:d:h:m:s]: 00:344:18:11:10
Block: 1017800 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246438 RingCT/type: yes/0
Extra: 0159e60d0a61523a9d9b070be48abeb15ab3e1c99424fd3c2ef811447e5647b7040211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caea42f64125f3852a29342d9153011b1a91a96c71bf06fd3ecd4e53ded31161 0.600000000000 1481585 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": 1017810, "vin": [ { "gen": { "height": 1017800 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caea42f64125f3852a29342d9153011b1a91a96c71bf06fd3ecd4e53ded31161" } } ], "extra": [ 1, 89, 230, 13, 10, 97, 82, 58, 157, 155, 7, 11, 228, 138, 190, 177, 90, 179, 225, 201, 148, 36, 253, 60, 46, 248, 17, 68, 126, 86, 71, 183, 4, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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