Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60f46e280a52c3065f66ab3cd8c20a0be51068e20c38858536d65e55b294fd8c

Tx prefix hash: 884d56cd98c94a9ba12ce272b29c5a0f4adf8bc1b7c8ca3635be6ce8c36dc374
Tx public key: 5ea2bb952cec1ca26aa2fc015f18f8f3bd95ca2004e5b5914f03f0c5c4fdf73b
Timestamp: 1746434272 Timestamp [UCT]: 2025-05-05 08:37:52 Age [y:d:h:m:s]: 00:272:03:23:32
Block: 1276185 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 192124 RingCT/type: yes/0
Extra: 015ea2bb952cec1ca26aa2fc015f18f8f3bd95ca2004e5b5914f03f0c5c4fdf73b0211000000099f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 39ba69f1055d4eb981aa214a12192b8c3b9cf9d3ea15fb319faa52a4c52695dd 0.600000000000 1763510 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": 1276195, "vin": [ { "gen": { "height": 1276185 } } ], "vout": [ { "amount": 600000000, "target": { "key": "39ba69f1055d4eb981aa214a12192b8c3b9cf9d3ea15fb319faa52a4c52695dd" } } ], "extra": [ 1, 94, 162, 187, 149, 44, 236, 28, 162, 106, 162, 252, 1, 95, 24, 248, 243, 189, 149, 202, 32, 4, 229, 181, 145, 79, 3, 240, 197, 196, 253, 247, 59, 2, 17, 0, 0, 0, 9, 159, 159, 230, 140, 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