Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 960f9197ce21251feaf74f408a1c042fb80026bbafe06803ea6c87455233f167

Tx prefix hash: 4fe39620f068f435636f1c79d94925851120d045b5676f51116910962a4f56f7
Tx public key: 25344b8f2fb873cb0179ebc096807c1b75cfc4088be34efd715c42cdb41d62f3
Timestamp: 1731897631 Timestamp [UCT]: 2024-11-18 02:40:31 Age [y:d:h:m:s]: 00:006:08:20:44
Block: 1156096 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4544 RingCT/type: yes/0
Extra: 0125344b8f2fb873cb0179ebc096807c1b75cfc4088be34efd715c42cdb41d62f3021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0bac8834e8d8b8baa5535adb87e0d585ca3b1d61cb33698ddf1d463d956f6a30 0.600000000000 1641719 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": 1156106, "vin": [ { "gen": { "height": 1156096 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0bac8834e8d8b8baa5535adb87e0d585ca3b1d61cb33698ddf1d463d956f6a30" } } ], "extra": [ 1, 37, 52, 75, 143, 47, 184, 115, 203, 1, 121, 235, 192, 150, 128, 124, 27, 117, 207, 196, 8, 139, 227, 78, 253, 113, 92, 66, 205, 180, 29, 98, 243, 2, 17, 0, 0, 0, 3, 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