Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: beb8fed66f9ddcea0d13db7c4e1b15818625639c3e84d8192081b3f0bde57119

Tx prefix hash: 651487c9e99b785c9c8bef26e1940bc3c42aa28adbbc1067b5aeae9d6fe5e82d
Tx public key: 0055d07b77dbf531cec30f801e5f456600cb77cc5be11321fb76ea12ca78744f
Timestamp: 1707934496 Timestamp [UCT]: 2024-02-14 18:14:56 Age [y:d:h:m:s]: 01:052:21:00:44
Block: 957518 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298832 RingCT/type: yes/0
Extra: 010055d07b77dbf531cec30f801e5f456600cb77cc5be11321fb76ea12ca78744f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3217b435baa695aaeb90fc005387a72a71254fd90f943d23f3d382c0f8bef7ab 0.600000000000 1416836 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": 957528, "vin": [ { "gen": { "height": 957518 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3217b435baa695aaeb90fc005387a72a71254fd90f943d23f3d382c0f8bef7ab" } } ], "extra": [ 1, 0, 85, 208, 123, 119, 219, 245, 49, 206, 195, 15, 128, 30, 95, 69, 102, 0, 203, 119, 204, 91, 225, 19, 33, 251, 118, 234, 18, 202, 120, 116, 79, 2, 17, 0, 0, 0, 1, 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