Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: daa765d7f60b1c110d022ee0bacbc27a7bb8e161bb37af27f76527b82a8d3f9e

Tx prefix hash: 134e37af5a8da6542f0f3a333174fcea2e3f28f4264fb1444c422a3cdd639848
Tx public key: 804fe9f0db96709a5bf3a876bfd7326008ff23e9212ae2d3a347474f3505f98b
Timestamp: 1708534422 Timestamp [UCT]: 2024-02-21 16:53:42 Age [y:d:h:m:s]: 01:046:09:48:47
Block: 962504 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294177 RingCT/type: yes/0
Extra: 01804fe9f0db96709a5bf3a876bfd7326008ff23e9212ae2d3a347474f3505f98b0211000000077a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 49f89c42488fa67fe327b9368a1e5f3341f2dba2a36160dcd2af0651056859df 0.600000000000 1422143 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": 962514, "vin": [ { "gen": { "height": 962504 } } ], "vout": [ { "amount": 600000000, "target": { "key": "49f89c42488fa67fe327b9368a1e5f3341f2dba2a36160dcd2af0651056859df" } } ], "extra": [ 1, 128, 79, 233, 240, 219, 150, 112, 154, 91, 243, 168, 118, 191, 215, 50, 96, 8, 255, 35, 233, 33, 42, 226, 211, 163, 71, 71, 79, 53, 5, 249, 139, 2, 17, 0, 0, 0, 7, 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