Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63fbf3e33d3fc80a8a0e820653f9087e1dddba5417d42d26698f2490650466cc

Tx prefix hash: 4a3f75e2b83dbc853fd7c6dd31e8477eb0d945ba5f08ae878ed6111cffe0d2de
Tx public key: 54230fe8f29ebc5d193043726860d8889c4602972b89a5c9c53a31a4a64e23c7
Timestamp: 1725229691 Timestamp [UCT]: 2024-09-01 22:28:11 Age [y:d:h:m:s]: 00:111:22:53:39
Block: 1100913 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80105 RingCT/type: yes/0
Extra: 0154230fe8f29ebc5d193043726860d8889c4602972b89a5c9c53a31a4a64e23c7021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 91d85d6ed16648170ccb57a33e34a352fd818a74f6fe069c31bfcb6269a2ee05 0.600000000000 1576894 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": 1100923, "vin": [ { "gen": { "height": 1100913 } } ], "vout": [ { "amount": 600000000, "target": { "key": "91d85d6ed16648170ccb57a33e34a352fd818a74f6fe069c31bfcb6269a2ee05" } } ], "extra": [ 1, 84, 35, 15, 232, 242, 158, 188, 93, 25, 48, 67, 114, 104, 96, 216, 136, 156, 70, 2, 151, 43, 137, 165, 201, 197, 58, 49, 164, 166, 78, 35, 199, 2, 17, 0, 0, 0, 5, 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