Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4c50bec68f73a12974695015bd3b7be8f81cad2b4b54a797ab7a77fe4bcc05

Tx prefix hash: 66a840c257b11aa12ffc4c3a4b18f99961a06ee53f0429f345f6e7a939a03a3e
Tx public key: 65b60f2c13b542cbe6ffd9eee89570596ed8db927379d8519bdcb2d20acfea9f
Timestamp: 1749621125 Timestamp [UCT]: 2025-06-11 05:52:05 Age [y:d:h:m:s]: 00:156:14:48:18
Block: 1302557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109636 RingCT/type: yes/0
Extra: 0165b60f2c13b542cbe6ffd9eee89570596ed8db927379d8519bdcb2d20acfea9f021100000006bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 209f1f32af5608e22c0f5444a55d979e867871f29061836d61bfd7e8dcc7dd32 0.600000000000 1790128 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": 1302567, "vin": [ { "gen": { "height": 1302557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "209f1f32af5608e22c0f5444a55d979e867871f29061836d61bfd7e8dcc7dd32" } } ], "extra": [ 1, 101, 182, 15, 44, 19, 181, 66, 203, 230, 255, 217, 238, 232, 149, 112, 89, 110, 216, 219, 146, 115, 121, 216, 81, 155, 220, 178, 210, 10, 207, 234, 159, 2, 17, 0, 0, 0, 6, 191, 81, 178, 162, 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