Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 206e5636e85fcca17f71d5f3231f953ee4b64a8fb753c2e647c9c590710adbf2

Tx prefix hash: 2925a4c0fba26119f61f470d68f48983ffe10a3598cf2d348fa56b7b54f97254
Tx public key: eb46741f86c968c2a67adb97f89274961e74ae9f9cb1233ed5496a40e2672e2f
Timestamp: 1719171003 Timestamp [UCT]: 2024-06-23 19:30:03 Age [y:d:h:m:s]: 00:277:20:05:51
Block: 1050668 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198542 RingCT/type: yes/0
Extra: 01eb46741f86c968c2a67adb97f89274961e74ae9f9cb1233ed5496a40e2672e2f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9f36911bab9d4e1555f9e63f7ef9ba19f4720ebe317037838e80fce36bd0a18b 0.600000000000 1520843 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": 1050678, "vin": [ { "gen": { "height": 1050668 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9f36911bab9d4e1555f9e63f7ef9ba19f4720ebe317037838e80fce36bd0a18b" } } ], "extra": [ 1, 235, 70, 116, 31, 134, 201, 104, 194, 166, 122, 219, 151, 248, 146, 116, 150, 30, 116, 174, 159, 156, 177, 35, 62, 213, 73, 106, 64, 226, 103, 46, 47, 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