Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e09e8ac5413080d9ec948f9fd841beb4951ba6251fffd76398f5074508b84ebc

Tx prefix hash: eb42ed2309bffd5757f214bca31009a15d17800d8d0ac5f1e917176db8dd50ad
Tx public key: 12c233cf57bb0184d1afceba4dbbf8ca55b88b2d60fa2d5f565af87c9a9b0419
Timestamp: 1749387620 Timestamp [UCT]: 2025-06-08 13:00:20 Age [y:d:h:m:s]: 00:164:01:12:14
Block: 1300644 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114927 RingCT/type: yes/0
Extra: 0112c233cf57bb0184d1afceba4dbbf8ca55b88b2d60fa2d5f565af87c9a9b0419021100000009bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8dd784c4fba417eea757b82915f43ac7e29ecd4d72537a8bf31c9f1a1a3b1f8b 0.600000000000 1788193 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": 1300654, "vin": [ { "gen": { "height": 1300644 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8dd784c4fba417eea757b82915f43ac7e29ecd4d72537a8bf31c9f1a1a3b1f8b" } } ], "extra": [ 1, 18, 194, 51, 207, 87, 187, 1, 132, 209, 175, 206, 186, 77, 187, 248, 202, 85, 184, 139, 45, 96, 250, 45, 95, 86, 90, 248, 124, 154, 155, 4, 25, 2, 17, 0, 0, 0, 9, 191, 81, 178, 162, 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