Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dea36b51a2b3576fd8f40b2fd4911c245ab979ea05838adb4eaaaf1ca6f6eabc

Tx prefix hash: a8a6aa15a781677e46f7a133e763b0c3ac44f1997978981d13be73c6e6900876
Tx public key: f7e9ac1be57444cf51bcf96398787c96d729bccb6e7609eb90217c1783945f03
Timestamp: 1709229655 Timestamp [UCT]: 2024-02-29 18:00:55 Age [y:d:h:m:s]: 01:051:23:56:13
Block: 968274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298168 RingCT/type: yes/0
Extra: 01f7e9ac1be57444cf51bcf96398787c96d729bccb6e7609eb90217c1783945f030211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac7f5fad5e018e85227838c3c3acd68cab3fd88b24d10d3f41d426792de7c802 0.600000000000 1428081 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": 968284, "vin": [ { "gen": { "height": 968274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac7f5fad5e018e85227838c3c3acd68cab3fd88b24d10d3f41d426792de7c802" } } ], "extra": [ 1, 247, 233, 172, 27, 229, 116, 68, 207, 81, 188, 249, 99, 152, 120, 124, 150, 215, 41, 188, 203, 110, 118, 9, 235, 144, 33, 124, 23, 131, 148, 95, 3, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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