Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3df1b7c342bde66abe897f0e8c6d3b9dae62e8b988356ab9369ae8c9a187389

Tx prefix hash: 4c447e93be3195b3ff5eb8df4f73dc85a74aac1250d9bef674ee2222666fde4f
Tx public key: 9af582df2937535bf28cf59289bd1b1845074cf6bf0c254739b50ba6355cb79a
Timestamp: 1756340167 Timestamp [UCT]: 2025-08-28 00:16:07 Age [y:d:h:m:s]: 00:091:22:13:42
Block: 1355918 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65645 RingCT/type: yes/0
Extra: 019af582df2937535bf28cf59289bd1b1845074cf6bf0c254739b50ba6355cb79a021100000002b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0923ed40f3f5a1b4ae3de3d2fa237810ad014163d09a93c5e23ee7cef5cbf871 0.600000000000 1843921 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": 1355928, "vin": [ { "gen": { "height": 1355918 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0923ed40f3f5a1b4ae3de3d2fa237810ad014163d09a93c5e23ee7cef5cbf871" } } ], "extra": [ 1, 154, 245, 130, 223, 41, 55, 83, 91, 242, 140, 245, 146, 137, 189, 27, 24, 69, 7, 76, 246, 191, 12, 37, 71, 57, 181, 11, 166, 53, 92, 183, 154, 2, 17, 0, 0, 0, 2, 178, 247, 132, 196, 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