Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 699aa99fa03a31e12b120c5f4f7bd3e19e78beefd49fe72ffd3eb6caf98542b9

Tx prefix hash: dac970737ac15f0f00c51b2b3915a326a2d7decb24df94e2413466d6915cdf0b
Tx public key: 0ae7132e86b2f74edc5d24bae1eb1f237cd12d541c1277361417e882fcd22542
Timestamp: 1713603056 Timestamp [UCT]: 2024-04-20 08:50:56 Age [y:d:h:m:s]: 00:256:04:02:29
Block: 1004502 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 183384 RingCT/type: yes/0
Extra: 010ae7132e86b2f74edc5d24bae1eb1f237cd12d541c1277361417e882fcd225420211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9a33cca7f1acae2f26de143b1d2ddadf9629010e949d4e8a66fd2a1bf0690ff 0.600000000000 1465070 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": 1004512, "vin": [ { "gen": { "height": 1004502 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9a33cca7f1acae2f26de143b1d2ddadf9629010e949d4e8a66fd2a1bf0690ff" } } ], "extra": [ 1, 10, 231, 19, 46, 134, 178, 247, 78, 220, 93, 36, 186, 225, 235, 31, 35, 124, 209, 45, 84, 28, 18, 119, 54, 20, 23, 232, 130, 252, 210, 37, 66, 2, 17, 0, 0, 0, 4, 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