Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b6169dbb561b50c7dee30fe11fef82953c87e16f941fee92bef5776bc0604c66

Tx prefix hash: 4cb866ace075608d9f9ac785d78f85fb89317af2f0f121b124dd9b776d3b08fe
Tx public key: 5cb46b2b903a80c1d3320bc8871ed940583fe31580ef3dc542d92487f62de18b
Timestamp: 1755141271 Timestamp [UCT]: 2025-08-14 03:14:31 Age [y:d:h:m:s]: 00:047:16:00:48
Block: 1346444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 33470 RingCT/type: yes/0
Extra: 015cb46b2b903a80c1d3320bc8871ed940583fe31580ef3dc542d92487f62de18b021100000005b2f784c4000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6d8237812840b4a04607d1296f8834de23cf876b39d4e47dc0f8d1ea910edc38 0.600000000000 1834345 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": 1346454, "vin": [ { "gen": { "height": 1346444 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6d8237812840b4a04607d1296f8834de23cf876b39d4e47dc0f8d1ea910edc38" } } ], "extra": [ 1, 92, 180, 107, 43, 144, 58, 128, 193, 211, 50, 11, 200, 135, 30, 217, 64, 88, 63, 227, 21, 128, 239, 61, 197, 66, 217, 36, 135, 246, 45, 225, 139, 2, 17, 0, 0, 0, 5, 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