Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442ea17a195abac739723284009886604cf7fe6663f06c122c56f2378a9f7829

Tx prefix hash: a71980f75a1a1e5dcb42d72e66b55a7143578e6d5461e8cd396e3eb51fdef2f3
Tx public key: 27b9e8f4eca888e4b8f7213ecacde25a7b964ad474b61fc18027afe5f5db86c1
Timestamp: 1708020088 Timestamp [UCT]: 2024-02-15 18:01:28 Age [y:d:h:m:s]: 00:332:08:12:04
Block: 958227 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237923 RingCT/type: yes/0
Extra: 0127b9e8f4eca888e4b8f7213ecacde25a7b964ad474b61fc18027afe5f5db86c102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3f4f44bb2159797c40509a0ca37d3841b5a3d585e1b656f9a7764151375f0d4c 0.600000000000 1417586 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": 958237, "vin": [ { "gen": { "height": 958227 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3f4f44bb2159797c40509a0ca37d3841b5a3d585e1b656f9a7764151375f0d4c" } } ], "extra": [ 1, 39, 185, 232, 244, 236, 168, 136, 228, 184, 247, 33, 62, 202, 205, 226, 90, 123, 150, 74, 212, 116, 182, 31, 193, 128, 39, 175, 229, 245, 219, 134, 193, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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