Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c06b44d1a37d53e19ada0f88db6b50e71a80952ced4c444289d10924fbaf85e

Tx prefix hash: 9ebbfc73ea3d5db13f3abe4d17716933dada7c39c4c5979c711624388cc70fa9
Tx public key: be3cb0a75ef9cecbfc121e7d9a953744fe4edbab556211859643e17db9a0b2b4
Timestamp: 1684968638 Timestamp [UCT]: 2023-05-24 22:50:38 Age [y:d:h:m:s]: 02:193:15:28:05
Block: 767385 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658237 RingCT/type: yes/0
Extra: 01be3cb0a75ef9cecbfc121e7d9a953744fe4edbab556211859643e17db9a0b2b4021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.759280610000 dcy

stealth address amount amount idx
00: 32255a4fe3037de19a0bdaa603cac8476b50a30c7bbfc1c1f2cbc02501bbd48a 1.759280610000 1216506 of 0

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": 767395, "vin": [ { "gen": { "height": 767385 } } ], "vout": [ { "amount": 1759280610, "target": { "key": "32255a4fe3037de19a0bdaa603cac8476b50a30c7bbfc1c1f2cbc02501bbd48a" } } ], "extra": [ 1, 190, 60, 176, 167, 94, 249, 206, 203, 252, 18, 30, 125, 154, 149, 55, 68, 254, 78, 219, 171, 85, 98, 17, 133, 150, 67, 225, 125, 185, 160, 178, 180, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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