Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6a67be717892e28416b055731e7fb914a9a3bddb7fad9d9f0c05f6b5bb74aa0f

Tx prefix hash: 16f35655da6cdefe35d543c7c0705100ce33a342a2c90ba0af7546dcfe5ea464
Tx public key: c3383f547472e48f10ba2d7017b0475d415f93fe6ff1fa17808636cbcd1107ab
Timestamp: 1706603378 Timestamp [UCT]: 2024-01-30 08:29:38 Age [y:d:h:m:s]: 01:294:20:05:44
Block: 946472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469533 RingCT/type: yes/0
Extra: 01c3383f547472e48f10ba2d7017b0475d415f93fe6ff1fa17808636cbcd1107ab021100000001c5452960000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7226f3d51f3ab72df10273469bce58d25b4b6818bd6f2a4f7c2ab7f99a9fa1e1 0.600000000000 1404804 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": 946482, "vin": [ { "gen": { "height": 946472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7226f3d51f3ab72df10273469bce58d25b4b6818bd6f2a4f7c2ab7f99a9fa1e1" } } ], "extra": [ 1, 195, 56, 63, 84, 116, 114, 228, 143, 16, 186, 45, 112, 23, 176, 71, 93, 65, 95, 147, 254, 111, 241, 250, 23, 128, 134, 54, 203, 205, 17, 7, 171, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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