Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 658d078cdb99d9f8c8183aa08d1326781ad21eb392bcc4aa862fda76387f2d73

Tx prefix hash: 2e448659f9977c49b5db471dc5104a8a123f5cc0e84d14f35895c7aa9dd5069e
Tx public key: 3c828802888ea1ea328a7c2859587ca76d632c205f5ff36abf23cde8a6743ba8
Timestamp: 1694382695 Timestamp [UCT]: 2023-09-10 21:51:35 Age [y:d:h:m:s]: 01:247:01:16:17
Block: 845359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437703 RingCT/type: yes/0
Extra: 013c828802888ea1ea328a7c2859587ca76d632c205f5ff36abf23cde8a6743ba80211000000074b8f5122000000000000000000

1 output(s) for total of 0.970453591000 dcy

stealth address amount amount idx
00: 2564cc903f0a41f655eecab41ccfcb38bca2aab38d3e451e04451fb301ff8f0a 0.970453591000 1298735 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": 845369, "vin": [ { "gen": { "height": 845359 } } ], "vout": [ { "amount": 970453591, "target": { "key": "2564cc903f0a41f655eecab41ccfcb38bca2aab38d3e451e04451fb301ff8f0a" } } ], "extra": [ 1, 60, 130, 136, 2, 136, 142, 161, 234, 50, 138, 124, 40, 89, 88, 124, 167, 109, 99, 44, 32, 95, 95, 243, 106, 191, 35, 205, 232, 166, 116, 59, 168, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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