Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be2bfa80749c86313d8bc0e6160813ce7bb0a4204d812b2a1ad1f0e9f05d4c0f

Tx prefix hash: 0b62acd25d49e78bfa7eec5f15469398cc3afe930869e457a6d743a9d729f6e7
Tx public key: e2e58670f5da7ea0cfdf1704f44711f862913ff88ac8f3b25116d35c5aaf2b4c
Timestamp: 1707756617 Timestamp [UCT]: 2024-02-12 16:50:17 Age [y:d:h:m:s]: 01:050:06:07:02
Block: 956046 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296949 RingCT/type: yes/0
Extra: 01e2e58670f5da7ea0cfdf1704f44711f862913ff88ac8f3b25116d35c5aaf2b4c0211000000140011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5689d68011c8278757ac2d8a6ec8b86ff243737100dcc5f6560d3fb934d72972 0.600000000000 1415348 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": 956056, "vin": [ { "gen": { "height": 956046 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5689d68011c8278757ac2d8a6ec8b86ff243737100dcc5f6560d3fb934d72972" } } ], "extra": [ 1, 226, 229, 134, 112, 245, 218, 126, 160, 207, 223, 23, 4, 244, 71, 17, 248, 98, 145, 63, 248, 138, 200, 243, 178, 81, 22, 211, 92, 90, 175, 43, 76, 2, 17, 0, 0, 0, 20, 0, 17, 5, 91, 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