Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 643ccfae1aea339f93d4e57d9ab53ea3030c6678ad58322e14b8250b28a8113f

Tx prefix hash: 414287f20ed3659eec9e07ec0d59595c482ca78f13b306b48737166eae65fad7
Tx public key: c2e1ac8057d6c38d0774d41e821a658576b9d6d44ed143639fd7e3c3c4188d09
Timestamp: 1708254653 Timestamp [UCT]: 2024-02-18 11:10:53 Age [y:d:h:m:s]: 01:093:23:55:21
Block: 960182 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328247 RingCT/type: yes/0
Extra: 01c2e1ac8057d6c38d0774d41e821a658576b9d6d44ed143639fd7e3c3c4188d0902110000000a59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 656cc5e0aaee9b06d933c78751b4bc3b77826ed05db341c6c1daaecbb4b5dd0f 0.600000000000 1419743 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": 960192, "vin": [ { "gen": { "height": 960182 } } ], "vout": [ { "amount": 600000000, "target": { "key": "656cc5e0aaee9b06d933c78751b4bc3b77826ed05db341c6c1daaecbb4b5dd0f" } } ], "extra": [ 1, 194, 225, 172, 128, 87, 214, 195, 141, 7, 116, 212, 30, 130, 26, 101, 133, 118, 185, 214, 212, 78, 209, 67, 99, 159, 215, 227, 195, 196, 24, 141, 9, 2, 17, 0, 0, 0, 10, 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