Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d182a28a6b3c3a61a6d39c8beb25a3ff3376c5569fbb4def9848ae70d272bf8e

Tx prefix hash: d6e206f537af619fec942e923fc43925be70285589c95644819a38f8d3a7af79
Tx public key: 8050a67288a2e38e0b7fcd63cf83dfa483841ad692a0071390a5eea89270937b
Timestamp: 1710852979 Timestamp [UCT]: 2024-03-19 12:56:19 Age [y:d:h:m:s]: 01:056:08:31:36
Block: 981737 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 301275 RingCT/type: yes/0
Extra: 018050a67288a2e38e0b7fcd63cf83dfa483841ad692a0071390a5eea89270937b02110000001359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ab34cd2944a98e2d3f2f0364d67d80bc76bb764b77c1a7fcb9c5d95e49c55280 0.600000000000 1441834 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": 981747, "vin": [ { "gen": { "height": 981737 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ab34cd2944a98e2d3f2f0364d67d80bc76bb764b77c1a7fcb9c5d95e49c55280" } } ], "extra": [ 1, 128, 80, 166, 114, 136, 162, 227, 142, 11, 127, 205, 99, 207, 131, 223, 164, 131, 132, 26, 214, 146, 160, 7, 19, 144, 165, 238, 168, 146, 112, 147, 123, 2, 17, 0, 0, 0, 19, 89, 218, 211, 245, 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