Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd5496706e7e3aafba95a5a2b806af237c8a3416942bd60e5abaf657aba070c6

Tx prefix hash: 786e2909c8ba0cb0a5c1755db58388b03ff95cb5752f633ca0b19ddc561ef2ff
Tx public key: 1d6cf55254f42c5ce32a27b5106d678405a83c97bc17200ba52f215fbd69aa05
Timestamp: 1698387445 Timestamp [UCT]: 2023-10-27 06:17:25 Age [y:d:h:m:s]: 01:194:06:19:29
Block: 878597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 399851 RingCT/type: yes/0
Extra: 011d6cf55254f42c5ce32a27b5106d678405a83c97bc17200ba52f215fbd69aa0502110000000175e3f0e9000000000000000000

1 output(s) for total of 0.753084017000 dcy

stealth address amount amount idx
00: ef9a98ea13caba04e739aba267e421f9acca42fef44198d7b944c882f416d809 0.753084017000 1334055 of 0

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": 878607, "vin": [ { "gen": { "height": 878597 } } ], "vout": [ { "amount": 753084017, "target": { "key": "ef9a98ea13caba04e739aba267e421f9acca42fef44198d7b944c882f416d809" } } ], "extra": [ 1, 29, 108, 245, 82, 84, 244, 44, 92, 227, 42, 39, 181, 16, 109, 103, 132, 5, 168, 60, 151, 188, 23, 32, 11, 165, 47, 33, 95, 189, 105, 170, 5, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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