Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9f42c55796c4543ac33b4cb83baf86754600f762bad42ba520df220d06dea277

Tx prefix hash: 8578c5aee625e7e887a8c1861efb2e8bef88f24d3a786ba1b5d1e9463ff95569
Tx public key: 304d0d4f2d581bfc8c85890d310c71b91eab2db548a087f87a03a8a30c042c6b
Timestamp: 1755052623 Timestamp [UCT]: 2025-08-13 02:37:03 Age [y:d:h:m:s]: 00:099:02:10:27
Block: 1345789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 70221 RingCT/type: yes/0
Extra: 01304d0d4f2d581bfc8c85890d310c71b91eab2db548a087f87a03a8a30c042c6b021100000001ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d02d309a3602ee10f433a365b9615053438cc0443dcf18a76693f4dde3e7b074 0.600000000000 1833684 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": 1345799, "vin": [ { "gen": { "height": 1345789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d02d309a3602ee10f433a365b9615053438cc0443dcf18a76693f4dde3e7b074" } } ], "extra": [ 1, 48, 77, 13, 79, 45, 88, 27, 252, 140, 133, 137, 13, 49, 12, 113, 185, 30, 171, 45, 181, 72, 160, 135, 248, 122, 3, 168, 163, 12, 4, 44, 107, 2, 17, 0, 0, 0, 1, 173, 121, 72, 208, 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