Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667dbfcc92565319f533534b7e3f44b86b3fa73b879dcf5af6a9f38bd3ef1bd2

Tx prefix hash: 172e022fc6418c08f914a32bcdb77ac149a829624d7c933d838e137f867adfae
Tx public key: 7df065a096b8d0f9ba8bcaadaaa1a5c1ac34e17ab44d5acd20411490bb67ebca
Timestamp: 1705389033 Timestamp [UCT]: 2024-01-16 07:10:33 Age [y:d:h:m:s]: 01:348:10:51:53
Block: 936397 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 507930 RingCT/type: yes/0
Extra: 017df065a096b8d0f9ba8bcaadaaa1a5c1ac34e17ab44d5acd20411490bb67ebca02110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b1231661c1fe2eac9c34a8ee681abfc0ef1e9896722efdda7145801477e6873e 0.600000000000 1394421 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": 936407, "vin": [ { "gen": { "height": 936397 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b1231661c1fe2eac9c34a8ee681abfc0ef1e9896722efdda7145801477e6873e" } } ], "extra": [ 1, 125, 240, 101, 160, 150, 184, 208, 249, 186, 139, 202, 173, 170, 161, 165, 193, 172, 52, 225, 122, 180, 77, 90, 205, 32, 65, 20, 144, 187, 103, 235, 202, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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