Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7f9a125027382a2599306dd2b75692d10ee90b5078954998aea7f94609fd364

Tx prefix hash: 4ac9ab0ad4b0507f8f8441cb8aab2545eb0190f1340aa19baaee5768999fb1de
Tx public key: e07930dd52e93c0dea6fd59b9ba2f4008ef8cdeaa37122204bf6b2287d24868a
Timestamp: 1677419614 Timestamp [UCT]: 2023-02-26 13:53:34 Age [y:d:h:m:s]: 02:070:07:28:24
Block: 705433 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 571843 RingCT/type: yes/0
Extra: 01e07930dd52e93c0dea6fd59b9ba2f4008ef8cdeaa37122204bf6b2287d24868a02110000000183600029000000000000000000

1 output(s) for total of 2.822328343000 dcy

stealth address amount amount idx
00: 6938e26e5b40e3a3223617a2b9187e7442b55b7dc69fd38d1d6d40188e9fa686 2.822328343000 1149134 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": 705443, "vin": [ { "gen": { "height": 705433 } } ], "vout": [ { "amount": 2822328343, "target": { "key": "6938e26e5b40e3a3223617a2b9187e7442b55b7dc69fd38d1d6d40188e9fa686" } } ], "extra": [ 1, 224, 121, 48, 221, 82, 233, 60, 13, 234, 111, 213, 155, 155, 162, 244, 0, 142, 248, 205, 234, 163, 113, 34, 32, 75, 246, 178, 40, 125, 36, 134, 138, 2, 17, 0, 0, 0, 1, 131, 96, 0, 41, 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