Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c07d49380f4a3788ea5cba69da3445b642016e82d931e771ed463685e8bf1fd2

Tx prefix hash: 59972fb90c50ae4ef0e28678b10de8c94564547289b3271ffdcec0a5ef82a27a
Tx public key: 94ba8e02c126aea4a655617d2dc5409f3d3a629dd49df0c1e4fad2dc27d21803
Timestamp: 1709118147 Timestamp [UCT]: 2024-02-28 11:02:27 Age [y:d:h:m:s]: 01:250:20:28:03
Block: 967347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437998 RingCT/type: yes/0
Extra: 0194ba8e02c126aea4a655617d2dc5409f3d3a629dd49df0c1e4fad2dc27d218030211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a50686488c5e2e0e8c5e6b44099dbf7595718cdae44daff97fbdd31a52b5b649 0.600000000000 1427124 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": 967357, "vin": [ { "gen": { "height": 967347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a50686488c5e2e0e8c5e6b44099dbf7595718cdae44daff97fbdd31a52b5b649" } } ], "extra": [ 1, 148, 186, 142, 2, 193, 38, 174, 164, 166, 85, 97, 125, 45, 197, 64, 159, 61, 58, 98, 157, 212, 157, 240, 193, 228, 250, 210, 220, 39, 210, 24, 3, 2, 17, 0, 0, 0, 6, 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