Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7030e884b8196b54b8a62cb4805433be8eeb1912c3cd64f3e9621401d00099bc

Tx prefix hash: 297b3fbe38892674bdef3b084707910d3d8435bfb43a82507bd8df833948718c
Tx public key: f7d0c0a1f063326bd8e614708b84d5c82fb2865bd3a53c45bd680bff5a3e1551
Timestamp: 1721735703 Timestamp [UCT]: 2024-07-23 11:55:03 Age [y:d:h:m:s]: 00:282:16:13:32
Block: 1071937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201968 RingCT/type: yes/0
Extra: 01f7d0c0a1f063326bd8e614708b84d5c82fb2865bd3a53c45bd680bff5a3e1551021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a6935fa9e3ce7c11110785942b9d94c3c30aaba392cf0cfff42e4e21c27d3126 0.600000000000 1544342 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": 1071947, "vin": [ { "gen": { "height": 1071937 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a6935fa9e3ce7c11110785942b9d94c3c30aaba392cf0cfff42e4e21c27d3126" } } ], "extra": [ 1, 247, 208, 192, 161, 240, 99, 50, 107, 216, 230, 20, 112, 139, 132, 213, 200, 47, 178, 134, 91, 211, 165, 60, 69, 189, 104, 11, 255, 90, 62, 21, 81, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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