Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 409f6c9cd6901e643fb6f6d8e25f8ac45fcbf78ccc43114ae8f80f0f9c800a0a

Tx prefix hash: 40a5469664df69c7b9aafc571eed1bdecfb48d239684f1f7838958eada68d185
Tx public key: c1bd70795263e256d3f7efba15cf0738cc97883b1904fe993f0a2c91ba0d1762
Timestamp: 1713415547 Timestamp [UCT]: 2024-04-18 04:45:47 Age [y:d:h:m:s]: 00:209:06:14:47
Block: 1002953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 149816 RingCT/type: yes/0
Extra: 01c1bd70795263e256d3f7efba15cf0738cc97883b1904fe993f0a2c91ba0d176202110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78831eb1ffe43c378c796cbcd6c54325569cf8a696cbbf3fcc058e0f0608d66d 0.600000000000 1463483 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": 1002963, "vin": [ { "gen": { "height": 1002953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78831eb1ffe43c378c796cbcd6c54325569cf8a696cbbf3fcc058e0f0608d66d" } } ], "extra": [ 1, 193, 189, 112, 121, 82, 99, 226, 86, 211, 247, 239, 186, 21, 207, 7, 56, 204, 151, 136, 59, 25, 4, 254, 153, 63, 10, 44, 145, 186, 13, 23, 98, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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