Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6fac4f18ab1cd7fbad2c4716c03f3af15d116fe7763f0e9831c97d4d17bb90ae

Tx prefix hash: dd4730fe08617ad00e0b00dc60bb8491f6d9253e1d94f41061acc627013d76fb
Tx public key: d653efac0670bff182d7fe11f82c2f963acdb94f06cbb2f9bd1faa250fea7e51
Timestamp: 1745108214 Timestamp [UCT]: 2025-04-20 00:16:54 Age [y:d:h:m:s]: 00:203:02:32:49
Block: 1265212 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142860 RingCT/type: yes/0
Extra: 01d653efac0670bff182d7fe11f82c2f963acdb94f06cbb2f9bd1faa250fea7e510211000000106c98aa3d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77370cdbec4e12cb2a0aac77b9ff1bbca0643e129992e6b215462018cbe171a3 0.600000000000 1752415 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": 1265222, "vin": [ { "gen": { "height": 1265212 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77370cdbec4e12cb2a0aac77b9ff1bbca0643e129992e6b215462018cbe171a3" } } ], "extra": [ 1, 214, 83, 239, 172, 6, 112, 191, 241, 130, 215, 254, 17, 248, 44, 47, 150, 58, 205, 185, 79, 6, 203, 178, 249, 189, 31, 170, 37, 15, 234, 126, 81, 2, 17, 0, 0, 0, 16, 108, 152, 170, 61, 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