Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c624a53ceec9cfd0a0378fc216c420e59161e948819a2e9641d57a0ea7be4be

Tx prefix hash: 4a969ea7b92a2eb52999e717c7f604b750718b8942dce7d4321fc54cfd8b9d85
Tx public key: 524fcd7f5ff214cc57b76ee631d6c7ed26590c7ce4b47ec7bbdbf12dabd3968f
Timestamp: 1574195202 Timestamp [UCT]: 2019-11-19 20:26:42 Age [y:d:h:m:s]: 05:347:20:43:00
Block: 12769 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1389301 RingCT/type: yes/0
Extra: 01524fcd7f5ff214cc57b76ee631d6c7ed26590c7ce4b47ec7bbdbf12dabd3968f02110000000266a80d00000000000000000000

1 output(s) for total of 556.800173665000 dcy

stealth address amount amount idx
00: 8c0b8d5fc1b1c5a45ef6557bf5faf0ddc8107f2186a724ff33a92a3f2c3749a1 556.800173665000 14470 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": 12779, "vin": [ { "gen": { "height": 12769 } } ], "vout": [ { "amount": 556800173665, "target": { "key": "8c0b8d5fc1b1c5a45ef6557bf5faf0ddc8107f2186a724ff33a92a3f2c3749a1" } } ], "extra": [ 1, 82, 79, 205, 127, 95, 242, 20, 204, 87, 183, 110, 230, 49, 214, 199, 237, 38, 89, 12, 124, 228, 180, 126, 199, 187, 219, 241, 45, 171, 211, 150, 143, 2, 17, 0, 0, 0, 2, 102, 168, 13, 0, 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