Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e3eb6b5b66e5e494b75f10cdb62e3d80e02f5cf18e92d5aa3c2c45adbb09bc

Tx prefix hash: 27deb6a9b5cab269da87a7c71ebf5be08490aa9a8116ce87fd9de7e24a0b731b
Tx public key: bcfe5ed1914b2ad4c39015ff0557f4d43dae015383fab3fe96164e80d9c16c51
Timestamp: 1746358581 Timestamp [UCT]: 2025-05-04 11:36:21 Age [y:d:h:m:s]: 00:237:08:51:08
Block: 1275550 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167419 RingCT/type: yes/0
Extra: 01bcfe5ed1914b2ad4c39015ff0557f4d43dae015383fab3fe96164e80d9c16c510211000000049f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aed76f24b190150ed593d5f4af81cc9795a1deb3e1ce3387236578e95f92065a 0.600000000000 1762865 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": 1275560, "vin": [ { "gen": { "height": 1275550 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aed76f24b190150ed593d5f4af81cc9795a1deb3e1ce3387236578e95f92065a" } } ], "extra": [ 1, 188, 254, 94, 209, 145, 75, 42, 212, 195, 144, 21, 255, 5, 87, 244, 212, 61, 174, 1, 83, 131, 250, 179, 254, 150, 22, 78, 128, 217, 193, 108, 81, 2, 17, 0, 0, 0, 4, 159, 159, 230, 140, 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