Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7fcabce0ddaa9a944b8e3ad9056dc376f4f917bfb46c388336f44996508f10c8

Tx prefix hash: 1194cbbdda2a2d0dfa2d349409bb91b06e61ad1dc3967fc89eee91161be34415
Tx public key: cf2ca2b8e5c20775a9b25f9877d249865541e94fd60c712faccee95d11108088
Timestamp: 1657966742 Timestamp [UCT]: 2022-07-16 10:19:02 Age [y:d:h:m:s]: 02:189:14:31:05
Block: 544935 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 656859 RingCT/type: yes/0
Extra: 01cf2ca2b8e5c20775a9b25f9877d249865541e94fd60c712faccee95d111080880211000000022e6b1fd5000000000000000000

1 output(s) for total of 9.602941239000 dcy

stealth address amount amount idx
00: b0d54fb3e1ac19f8ab655434e00afedcf8ec805daf309784d4e1592d3b1e160d 9.602941239000 975772 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": 544945, "vin": [ { "gen": { "height": 544935 } } ], "vout": [ { "amount": 9602941239, "target": { "key": "b0d54fb3e1ac19f8ab655434e00afedcf8ec805daf309784d4e1592d3b1e160d" } } ], "extra": [ 1, 207, 44, 162, 184, 229, 194, 7, 117, 169, 178, 95, 152, 119, 210, 73, 134, 85, 65, 233, 79, 214, 12, 113, 47, 172, 206, 233, 93, 17, 16, 128, 136, 2, 17, 0, 0, 0, 2, 46, 107, 31, 213, 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