Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e933e0574baabe485f23ca90d578f797de971c3e3c257e636383a1725f38630

Tx prefix hash: dd6c7d8ad9ae78aee180b080e7f5e353d0ec78de4d9474393c605fb15ac86b39
Tx public key: d6a4b26ef9f76598d725b458c77c5e4b6aa90c74580c23b1656b8209dfc6ef43
Timestamp: 1749659260 Timestamp [UCT]: 2025-06-11 16:27:40 Age [y:d:h:m:s]: 00:151:23:41:20
Block: 1302882 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 106315 RingCT/type: yes/0
Extra: 01d6a4b26ef9f76598d725b458c77c5e4b6aa90c74580c23b1656b8209dfc6ef430211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cf144ed82fab3dd70044e2173e87eb2fd6409437dce1fd541bb023205d67e66 0.600000000000 1790455 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": 1302892, "vin": [ { "gen": { "height": 1302882 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cf144ed82fab3dd70044e2173e87eb2fd6409437dce1fd541bb023205d67e66" } } ], "extra": [ 1, 214, 164, 178, 110, 249, 247, 101, 152, 215, 37, 180, 88, 199, 124, 94, 75, 106, 169, 12, 116, 88, 12, 35, 177, 101, 107, 130, 9, 223, 198, 239, 67, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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