Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a17a52a1cccf722f1270f7215516f91d563c19b55f6d2df75ab9b13e23e6393e

Tx prefix hash: 021fee064577d864769df15e6ec63743a9204f9bc8f48610b0c3edc5d371df6c
Tx public key: e2a23711f7c9a85406cf1308f896de866887fcdbcbadf6d0a8624e85398c7189
Timestamp: 1673526462 Timestamp [UCT]: 2023-01-12 12:27:42 Age [y:d:h:m:s]: 02:270:21:42:02
Block: 673126 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712965 RingCT/type: yes/0
Extra: 01e2a23711f7c9a85406cf1308f896de866887fcdbcbadf6d0a8624e85398c71890211000000018b7b6602000000000000000000

1 output(s) for total of 3.611221162000 dcy

stealth address amount amount idx
00: 0f86371851cf6da0513e0aea4963fae260aca9e8006c71294049a0f8ed3f5c36 3.611221162000 1114715 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": 673136, "vin": [ { "gen": { "height": 673126 } } ], "vout": [ { "amount": 3611221162, "target": { "key": "0f86371851cf6da0513e0aea4963fae260aca9e8006c71294049a0f8ed3f5c36" } } ], "extra": [ 1, 226, 162, 55, 17, 247, 201, 168, 84, 6, 207, 19, 8, 248, 150, 222, 134, 104, 135, 252, 219, 203, 173, 246, 208, 168, 98, 78, 133, 57, 140, 113, 137, 2, 17, 0, 0, 0, 1, 139, 123, 102, 2, 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