Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e80a463091aed77b78d11d6c810c2ba21ef5c39358b6c95d4ac98b512925a9d5

Tx prefix hash: 7cff4a7d25b68e508cec5cf103eea5e77f3315fe94366b7d514c1a90090fe0a7
Tx public key: f88aa68f27d6b8e2133cab663b9a8408094e237bf492c3573002015c44ca7393
Timestamp: 1733643639 Timestamp [UCT]: 2024-12-08 07:40:39 Age [y:d:h:m:s]: 00:334:13:11:57
Block: 1170571 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236612 RingCT/type: yes/0
Extra: 01f88aa68f27d6b8e2133cab663b9a8408094e237bf492c3573002015c44ca7393021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 528aed851cc982844dcf0c4ccfbeb0b1cd285557ab345e3880e833e120a8cece 0.600000000000 1656302 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": 1170581, "vin": [ { "gen": { "height": 1170571 } } ], "vout": [ { "amount": 600000000, "target": { "key": "528aed851cc982844dcf0c4ccfbeb0b1cd285557ab345e3880e833e120a8cece" } } ], "extra": [ 1, 248, 138, 166, 143, 39, 214, 184, 226, 19, 60, 171, 102, 59, 154, 132, 8, 9, 78, 35, 123, 244, 146, 195, 87, 48, 2, 1, 92, 68, 202, 115, 147, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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