Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a80f830332d2369c5f3594910b908261b6f10434bd5170b5aee8c0e14c14f0a6

Tx prefix hash: 63de1b9a483a60be70891d1ecc0603aed1259883f5fc707689d120f3a95de565
Tx public key: b32922dd59cbc6e862aea4032af89bfb897a471abab6ae2da5eb1340acd8798d
Timestamp: 1716315279 Timestamp [UCT]: 2024-05-21 18:14:39 Age [y:d:h:m:s]: 00:235:11:24:38
Block: 1027006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 168528 RingCT/type: yes/0
Extra: 01b32922dd59cbc6e862aea4032af89bfb897a471abab6ae2da5eb1340acd8798d0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.615580000000 dcy

stealth address amount amount idx
00: e05ca0de73addc80986def5dc364677b0e18bffeee066d4cffa141e0c2e4f789 0.615580000000 1494401 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": 1027016, "vin": [ { "gen": { "height": 1027006 } } ], "vout": [ { "amount": 615580000, "target": { "key": "e05ca0de73addc80986def5dc364677b0e18bffeee066d4cffa141e0c2e4f789" } } ], "extra": [ 1, 179, 41, 34, 221, 89, 203, 198, 232, 98, 174, 164, 3, 42, 248, 155, 251, 137, 122, 71, 26, 186, 182, 174, 45, 165, 235, 19, 64, 172, 216, 121, 141, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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