Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bfc8bed7e8187204a7d805cebbba5a4315145563b0878dd5af98ac63d77fa718

Tx prefix hash: 00adf83413a1cf77a8d054f7e02ac79fa2e5e18cbf15bf6db16b620ef083cb9d
Tx public key: 99b2aa7882a64fda160c2fb6f2bfe30f5eae8584b3ed455b324142abeddcbd15
Timestamp: 1759051958 Timestamp [UCT]: 2025-09-28 09:32:38 Age [y:d:h:m:s]: 00:101:00:47:08
Block: 1378193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72355 RingCT/type: yes/0
Extra: 0199b2aa7882a64fda160c2fb6f2bfe30f5eae8584b3ed455b324142abeddcbd15021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 814006e019c8091754a1832b0bedfe84e31c01cd963521d0e2a9fa1223c32939 0.600000000000 1866288 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": 1378203, "vin": [ { "gen": { "height": 1378193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "814006e019c8091754a1832b0bedfe84e31c01cd963521d0e2a9fa1223c32939" } } ], "extra": [ 1, 153, 178, 170, 120, 130, 166, 79, 218, 22, 12, 47, 182, 242, 191, 227, 15, 94, 174, 133, 132, 179, 237, 69, 91, 50, 65, 66, 171, 237, 220, 189, 21, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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