Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27f7a291c8b4ba51185beff9659bed5510fac782c83ffe9c6371766dff4691ac

Tx prefix hash: 031210bf5a79f542012d46ffac16997c95d435c1afbf2d6c7ac743e98e59f018
Tx public key: 25ae9dc700773569472eef9ed94b71209b71894402a92ff4bec8a6c892a63d2a
Timestamp: 1698393520 Timestamp [UCT]: 2023-10-27 07:58:40 Age [y:d:h:m:s]: 02:096:02:24:58
Block: 878646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 588188 RingCT/type: yes/0
Extra: 0125ae9dc700773569472eef9ed94b71209b71894402a92ff4bec8a6c892a63d2a021100000009e6d27f9c000000000000000000

1 output(s) for total of 0.752802536000 dcy

stealth address amount amount idx
00: 7337aef7ef9379a4ea46b6dbb68225cd406673e603b45a64f9f0029052c88abc 0.752802536000 1334110 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": 878656, "vin": [ { "gen": { "height": 878646 } } ], "vout": [ { "amount": 752802536, "target": { "key": "7337aef7ef9379a4ea46b6dbb68225cd406673e603b45a64f9f0029052c88abc" } } ], "extra": [ 1, 37, 174, 157, 199, 0, 119, 53, 105, 71, 46, 239, 158, 217, 75, 113, 32, 155, 113, 137, 68, 2, 169, 47, 244, 190, 200, 166, 200, 146, 166, 61, 42, 2, 17, 0, 0, 0, 9, 230, 210, 127, 156, 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