Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d35d91c7ac1c004ecf957cfbd619b3ca0df21505b744380f75a7baa9fe1cc73a

Tx prefix hash: 5b72ccb4080f3ca59e46fa15c06b1111aa6f1850552cd21bafb31ccb314d4112
Tx public key: fd6ac635e270e6ca34e0ece997c81434831f2fb6534b3b17203d08e04b4d8c9a
Timestamp: 1759211664 Timestamp [UCT]: 2025-09-30 05:54:24 Age [y:d:h:m:s]: 00:008:01:03:19
Block: 1379506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5772 RingCT/type: yes/0
Extra: 01fd6ac635e270e6ca34e0ece997c81434831f2fb6534b3b17203d08e04b4d8c9a02110000000397baf922000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb87bae16d53a06885869b2b93556e132af0c59d5ce3a02b82f0300bd1d9ebf2 0.600000000000 1867603 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": 1379516, "vin": [ { "gen": { "height": 1379506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb87bae16d53a06885869b2b93556e132af0c59d5ce3a02b82f0300bd1d9ebf2" } } ], "extra": [ 1, 253, 106, 198, 53, 226, 112, 230, 202, 52, 224, 236, 233, 151, 200, 20, 52, 131, 31, 47, 182, 83, 75, 59, 23, 32, 61, 8, 224, 75, 77, 140, 154, 2, 17, 0, 0, 0, 3, 151, 186, 249, 34, 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