Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26bed26e7e253939451224a1dbfdbcff004b1d62c099f60d9bed4652914fba79

Tx prefix hash: 10db84e92cf1e9d7ce9fa45f2da1f285d2ca6457502cfcb174d23fdbeb4482fd
Tx public key: 478b94ba2c421b1d2b2c1db8d1098628003fbd53f712bf4e1cee2d335813c65c
Timestamp: 1760236237 Timestamp [UCT]: 2025-10-12 02:30:37 Age [y:d:h:m:s]: 00:039:05:48:26
Block: 1388011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 28102 RingCT/type: yes/0
Extra: 01478b94ba2c421b1d2b2c1db8d1098628003fbd53f712bf4e1cee2d335813c65c021100000006163191ee000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 19b88099ac7fc8eff1cfbaa1516f7b37ae3e33c58707731f440df57b891db2fb 0.600000000000 1876206 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": 1388021, "vin": [ { "gen": { "height": 1388011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "19b88099ac7fc8eff1cfbaa1516f7b37ae3e33c58707731f440df57b891db2fb" } } ], "extra": [ 1, 71, 139, 148, 186, 44, 66, 27, 29, 43, 44, 29, 184, 209, 9, 134, 40, 0, 63, 189, 83, 247, 18, 191, 78, 28, 238, 45, 51, 88, 19, 198, 92, 2, 17, 0, 0, 0, 6, 22, 49, 145, 238, 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