Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: caf7b2fb32e321fe6cdc160464b7dc1cc417142a20c4f6e99d7f4e20fb538b49

Tx prefix hash: 4e85a7846777c2d6d7005da00d12ec6f488ca66c639d65b875f32c8532c75c22
Tx public key: 13cae21833df5ab7f865d6a045af601cf6c07494ddd368934003e45cec8b43db
Timestamp: 1720442626 Timestamp [UCT]: 2024-07-08 12:43:46 Age [y:d:h:m:s]: 00:277:01:05:31
Block: 1061233 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 197944 RingCT/type: yes/0
Extra: 0113cae21833df5ab7f865d6a045af601cf6c07494ddd368934003e45cec8b43db021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9633dd969ce8838e13be5c09b493a5a42e3b46df7c3201c83825ea7c425ecfc3 0.600000000000 1531724 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": 1061243, "vin": [ { "gen": { "height": 1061233 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9633dd969ce8838e13be5c09b493a5a42e3b46df7c3201c83825ea7c425ecfc3" } } ], "extra": [ 1, 19, 202, 226, 24, 51, 223, 90, 183, 248, 101, 214, 160, 69, 175, 96, 28, 246, 192, 116, 148, 221, 211, 104, 147, 64, 3, 228, 92, 236, 139, 67, 219, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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