Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 280feb5eb4f9fcad6e5304ede2e795c0ee0a7726f18e9c2596b4c5369a849221

Tx prefix hash: eb02df051bcc06cb3d4dd3c179734ad5fc6c3e561d052b433a26ad779e17a8cd
Tx public key: 2e9144a0f48424540512f82cd31086fcd6c31eb68a703e53bc860a8c3ca34c33
Timestamp: 1765889543 Timestamp [UCT]: 2025-12-16 12:52:23 Age [y:d:h:m:s]: 00:007:14:47:39
Block: 1434862 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 5453 RingCT/type: yes/0
Extra: 012e9144a0f48424540512f82cd31086fcd6c31eb68a703e53bc860a8c3ca34c33021100000006d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0f7cefbef054fcf0d6672065bc93a736b831a8812ec7ea867e4e692ed26c82f 0.600000000000 1923659 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": 1434872, "vin": [ { "gen": { "height": 1434862 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0f7cefbef054fcf0d6672065bc93a736b831a8812ec7ea867e4e692ed26c82f" } } ], "extra": [ 1, 46, 145, 68, 160, 244, 132, 36, 84, 5, 18, 248, 44, 211, 16, 134, 252, 214, 195, 30, 182, 138, 112, 62, 83, 188, 134, 10, 140, 60, 163, 76, 51, 2, 17, 0, 0, 0, 6, 214, 225, 157, 124, 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