Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 217ea1d90f229aad1ab703c37d4dff3c0fad492a2bbe3848e1a2c675b6d16e92

Tx prefix hash: 042bd59c167e6f44f16091459e8ec6e43f83da0ea75ef93eb63e9244be9509dd
Tx public key: f77a7b33c4228f37e6f926fcd4ad29ee7f95983a8eec6fb327dd26798077697c
Timestamp: 1760917517 Timestamp [UCT]: 2025-10-19 23:45:17 Age [y:d:h:m:s]: 00:076:10:33:39
Block: 1393681 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54730 RingCT/type: yes/0
Extra: 01f77a7b33c4228f37e6f926fcd4ad29ee7f95983a8eec6fb327dd26798077697c02110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f7bc4521dd1a10fcec05ec6810f4a0af82cee432356f29818058d13a95809a2 0.600000000000 1881946 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": 1393691, "vin": [ { "gen": { "height": 1393681 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f7bc4521dd1a10fcec05ec6810f4a0af82cee432356f29818058d13a95809a2" } } ], "extra": [ 1, 247, 122, 123, 51, 196, 34, 143, 55, 230, 249, 38, 252, 212, 173, 41, 238, 127, 149, 152, 58, 142, 236, 111, 179, 39, 221, 38, 121, 128, 119, 105, 124, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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