Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dffe9c22b41546ac9a0d833759b7abd58981563a2e1f223b4f143b05b463d059

Tx prefix hash: ac4f418850b4ac98e849a5f4cadc9c425738eff7e423f908cb9e6e26b75227b7
Tx public key: 936aa14734eccc332ff85092a7cfabdeee919f368cff4cbe4978d021b49cb712
Timestamp: 1716931498 Timestamp [UCT]: 2024-05-28 21:24:58 Age [y:d:h:m:s]: 00:316:15:11:40
Block: 1032134 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 226287 RingCT/type: yes/0
Extra: 01936aa14734eccc332ff85092a7cfabdeee919f368cff4cbe4978d021b49cb71202110000000541ee1c9b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f758f10a20fcb00f5da543d802b5a9c4d7e8b809660203721535551f780c50b9 0.600000000000 1500583 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": 1032144, "vin": [ { "gen": { "height": 1032134 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f758f10a20fcb00f5da543d802b5a9c4d7e8b809660203721535551f780c50b9" } } ], "extra": [ 1, 147, 106, 161, 71, 52, 236, 204, 51, 47, 248, 80, 146, 167, 207, 171, 222, 238, 145, 159, 54, 140, 255, 76, 190, 73, 120, 208, 33, 180, 156, 183, 18, 2, 17, 0, 0, 0, 5, 65, 238, 28, 155, 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