Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 53561471bf56cbb6f9ade0d32938012e6db1421704ae196d1a0bfc90746ef9ac

Tx prefix hash: 5f966a77a8fa5bd183dba6cd00f3f0fc59e92d2b4178b6ddd5ac0ec0165fdc13
Tx public key: cf9c380bfa7792874d0488f9da74b45c26250bebcc2e45abff31ce6b78d969ae
Timestamp: 1704870723 Timestamp [UCT]: 2024-01-10 07:12:03 Age [y:d:h:m:s]: 01:107:13:41:54
Block: 932116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337996 RingCT/type: yes/0
Extra: 01cf9c380bfa7792874d0488f9da74b45c26250bebcc2e45abff31ce6b78d969ae0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33bf42dc4ca230b43e84d5b8ba997e598df78d266b2e3199a971c3f3a3b12e12 0.600000000000 1390038 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": 932126, "vin": [ { "gen": { "height": 932116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33bf42dc4ca230b43e84d5b8ba997e598df78d266b2e3199a971c3f3a3b12e12" } } ], "extra": [ 1, 207, 156, 56, 11, 250, 119, 146, 135, 77, 4, 136, 249, 218, 116, 180, 92, 38, 37, 11, 235, 204, 46, 69, 171, 255, 49, 206, 107, 120, 217, 105, 174, 2, 17, 0, 0, 0, 5, 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