Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c9b5feb6e13fdefc3b59f06a82cfbd7e40fa281ba3717b268564dacbdb8a1cbf

Tx prefix hash: 2ba9ed49c778a183f8fa5473460b50ccaefa95d05ad6f6b53f783be79aa57006
Tx public key: 8370528eb8e82ff24f73d962abdfc85f831bd68223f2e3c5b364d1f36480af20
Timestamp: 1698520620 Timestamp [UCT]: 2023-10-28 19:17:00 Age [y:d:h:m:s]: 01:179:04:29:58
Block: 879689 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389085 RingCT/type: yes/0
Extra: 018370528eb8e82ff24f73d962abdfc85f831bd68223f2e3c5b364d1f36480af2002110000000575e3f0e9000000000000000000

1 output(s) for total of 0.746835889000 dcy

stealth address amount amount idx
00: ba50af79669c3b80b3909f8dae5688ad0f60ca44b1514465d57623d966c02e6f 0.746835889000 1335225 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": 879699, "vin": [ { "gen": { "height": 879689 } } ], "vout": [ { "amount": 746835889, "target": { "key": "ba50af79669c3b80b3909f8dae5688ad0f60ca44b1514465d57623d966c02e6f" } } ], "extra": [ 1, 131, 112, 82, 142, 184, 232, 47, 242, 79, 115, 217, 98, 171, 223, 200, 95, 131, 27, 214, 130, 35, 242, 227, 197, 179, 100, 209, 243, 100, 128, 175, 32, 2, 17, 0, 0, 0, 5, 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